auto_resize_dimensions

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'fit content' without specifying that this modifies the spreadsheet, may overwrite existing manual row/column sizes, or requires write permissions. This lack of detail is significant for a mutation tool.

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 sentence of 6 words, which is concise and front-loaded. It avoids unnecessary details. However, given the tool's complexity (5 parameters), a slightly more verbose description could improve clarity without losing conciseness.

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?

The schema covers all parameters, but the description lacks important context such as what 'fit content' means (e.g., column width adjusts to longest cell content), whether it is destructive, and the effect on merged cells or formatting. The absence of an output schema is acceptable, but behavioral context is insufficient.

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?

All 5 parameters have descriptions in the input schema, achieving 100% coverage. The tool description adds no additional meaning beyond what the schema provides. Baseline score of 3 is appropriate since the schema already defines parameters clearly.

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 'Auto-resize columns or rows to fit content' clearly states the action (auto-resize) and the resource (columns/rows). It distinguishes the tool from sibling tools like delete_dimension or insert_dimension, which handle dimension structural changes, not resizing. However, it does not explicitly differentiate from any hypothetical resize-only tools.

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 description provides no guidance on when to use this tool versus alternatives, such as when to use manual formatting or other resize methods. There is no mention of prerequisites or when not to use this tool.

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