auto_resize_dimensions

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

No annotations provided, so the description should disclose behavioral traits. It states the action but does not mention side effects, permissions, or reversibility. The tool modifies dimensions, which is a write operation, but the description does not indicate this.

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 with a parenthetical clarification. Extremely concise with no wasted words.

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 the tool's complexity (auto-fitting a range of rows/columns) and no output schema, the description lacks details like allowed dimension values, error handling, and comparison with sibling 'auto_fit'. It is minimally adequate but leaves gaps.

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 description adds meaning to 'start_index' and 'end_index' by explaining they are zero-based and half-open, but does not clarify 'sheet', 'dimension' (expected values like 'ROWS'/'COLUMNS'), or 'spreadsheet_id'. Schema coverage is 0%, so more detail would be needed for a higher score.

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 clearly states the verb 'auto-fit' and resource 'columns or rows', and adds specificity with 'zero-based, half-open range'. It distinguishes from sibling 'auto_fit' by specifying a range, but does not explicitly differentiate.

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 like 'auto_fit' or 'set_dimension_size'. The description lacks context about prerequisites or constraints.

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