sheets_update_dimension_properties

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

With no annotations provided, the description must disclose behavioral traits; it only states the operations without addressing side effects (e.g., whether existing properties are overwritten), auth needs, or range semantics. This is a mutation tool missing key transparency details.

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, focused sentence that immediately communicates the tool's function without unnecessary words. It is concise and front-loaded, effectively covering the core operations.

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?

Despite having an output schema, the tool has 7 parameters with 0% schema coverage and no annotations. The description fails to clarify essential aspects like valid dimension values, index handling, and behavior when both pixel_size and hidden are provided. The tool is too complex for such a minimal description.

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 description coverage is 0%, so the description must compensate. It mentions pixel_size and hidden concepts, but does not explain semantics of start_index/end_index (e.g., zero-based, half-open) or the relationship between pixel_size and hidden. The description adds minimal value beyond the raw parameter names.

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 uses a specific verb 'Set' and clearly identifies the resource (column width / row height, hide/show rows/columns). It distinguishes this tool from sibling tools like insert/delete/move dimension by focusing on updating properties, making it unique and easy to select.

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 implies when to use the tool: whenever you need to resize or hide/show rows/columns. However, it does not explicitly mention exclusions or alternatives (e.g., when to use insert/delete dimension instead), leaving the usage context inferred rather than clearly stated.

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