Rename/resize ONE sheet of a Rootr spreadsheet

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

Description emphasizes that cells are not touched, which is critical for a mutation tool with destructiveHint=false. Adds value beyond annotations by clarifying the scope of the update.

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?

Two sentences, no redundancy. Front-loaded with action and scope. Efficient and direct.

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 mutation tool with 8 parameters and no output schema, the description covers purpose and prerequisite. Missing details like error conditions or concurrency, but acceptable given the tool's specificity.

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 hints at key parameters (name, dimensions, row-col sizing) which align with schema properties. Schema already covers 75% of parameters; description adds context but does not detail each parameter.

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?

Clearly states the tool performs a merge-patch on a single sheet's name, dimensions, and row-col sizing by sheetId, without affecting cells. Distinguishes from sibling tools like rootr_update_spreadsheet and rootr_patch_spreadsheet_cells.

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?

Explicitly instructs to call rootr_read_spreadsheet first to obtain the exact sheetId. Does not provide exclusions or alternatives, but the context makes the usage clear.

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