trpc_generate_client

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral disclosure burden. It only says 'Generate,' which suggests file creation, but it does not disclose whether files are overwritten, whether packages are installed, whether an existing project is required, or what side effects occur.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no filler or repetition. Every word adds meaning: 'Generate' indicates the action, 'tRPC client' identifies the resource, and 'with React Query' specifies the integration.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description should compensate but does not. It omits what files are generated, the expected project layout, whether api_key is required for authentication, and what the agent should observe after generation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is only 50%: 'directory' is documented but 'api_key' has no description. The tool description does not explain the purpose of api_key or how it relates to generating the tRPC client, leaving a required-vs-optional behavioral gap for the agent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: 'Generate tRPC client with React Query.' It clearly distinguishes this tool from nearby siblings like trpc_generate_router and trpc_add_middleware by stating it produces the client, not the server/router or middleware.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'Generate tRPC client with React Query' implies the tool is for creating a tRPC client that integrates React Query, so the basic use case is inferable. However, it does not explicitly state when to prefer this over trpc_generate_router or trpc_add_middleware, nor does it mention prerequisites such as an existing tRPC project.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.