write_sheet

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

Annotations indicate destructiveness; description adds detail on confirm requirement for overwriting, dry_run preview behavior, and value_input formula handling. Contradiction not present.

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?

Three sentences with front-loaded purpose. Efficient but could be slightly tighter; no redundancy.

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?

Covers key behaviors and parameters but omits output/return value and potential constraints like row limits. Adequate for basic use.

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 coverage 0% so description carries burden. Explains start_cell default, value_input options, confirm, dry_run, but leaves item, tab, rows structure unexplained. Adds partial value.

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 tool writes rows to a spreadsheet tab, with specific verb and resource. It distinguishes from siblings like append_rows by implying overwriting behavior and referencing start_cell.

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?

Provides context for confirm, dry_run, and value_input parameters, guiding when to use each. Lacks explicit when-not-to-use or alternatives, but context is clear.

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