rename

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

No behavioral traits disclosed (e.g., destructiveness, idempotency, auth needs). With no annotations, description carries full burden but provides none.

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?

Single sentence is concise but underspecifies the tool. Missing expansion on the 'unified' nature and batch capability.

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?

Given complex nested schema and output schema, description leaves out critical context like batch operations, expected return format, and usage examples.

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?

Description adds no meaning to parameters. Schema has 50% coverage, but the top-level description does not elaborate on 'batch' or 'instance_id' beyond what schema provides.

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?

Description clearly states it's a rename operation for functions, globals, locals, and stack variables, which is specific and actionable. However, it doesn't distinguish from siblings, but no sibling directly performs renaming.

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?

No guidance on when to use this tool vs alternatives. Lacks context for when not to use it or what prerequisites exist.

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