excel_rename_sheet

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

The description does not disclose that renaming may break formula references or affect other sheets, nor does it mention the optional backup parameter. Annotations indicate destructiveHint=true, but description adds no behavioral context.

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 extremely concise (3 words), but it sacrifices informational value and does not front-load key constraints or side effects.

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?

For a tool with 4 parameters, destructive annotation, and many siblings, the description is too sparse. It omits details about file path requirements, naming restrictions, and potential impacts on references.

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?

Schema descriptions cover 75% of parameters, and parameter names are self-explanatory. The description does not add meaning beyond what the schema provides, but does not actively mislead.

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 'Rename a sheet' is a tautology of the tool name, providing no additional context or differentiation from siblings like excel_duplicate_sheet or excel_create_sheet.

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 versus alternatives, no prerequisites or exclusions mentioned, leaving the agent to infer usage context.

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