tool-definition

You define Claude Code tools using a schema-first approach by calling the buildTool factory with a Zod inputSchema, applying permission checks, and returning { data } on success to ensure runtime validation and safe defaults.

The best way to add permission gating is by using a centralized pre-call permission check within a buildTool-based workflow, ensuring the check runs before tool execution to enforce safe tool composition.

Zod validation works by defining an inputSchema getter that ensures runtime validation and TypeScript types stay in sync, providing schema-first design for safe and reliable tool execution.

Yes, you can use buildTool to update existing tool behavior across projects by applying its repeatable pattern with default flags, mandatory inputSchema getters, and pre-call permission checks to maintain consistency.

A schema-first approach for tool definition ensures validation, permissions, and safe defaults are baked in from the start, keeping runtime validation and TypeScript types synchronized while preventing unsafe tool execution.

Yes, you need to return { data } on success when defining tools, which is a mandatory part of the buildTool-based workflow pattern to ensure consistent and safe output handling.