edit_spreadsheet

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

Beyond annotations, the description discloses the configuration requirement (allow_file_write) and the .xlsx-only restriction for create_if_missing. It does not explicitly warn that updates overwrite existing cell values, but this is largely inferred from the word 'write'.

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 efficiently structure the description with the main action first and parameter details following. Every sentence provides useful information without any wasteful repetition.

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 5-parameter write tool, the description covers the core workflows, parameter formats, configuration requirement, and format limitations. It is sufficiently complete for practical use, despite lacking an output schema.

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 schema descriptions cover all parameters, and the description adds concrete examples for updates and append_rows, clarifies A1 notation, and explains the create_if_missing behavior. This adds meaningful value beyond the schema.

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 cells or appends rows to spreadsheet files and specifies the supported formats (.xlsx or .csv). This distinguishes it from sibling file operations like write_file or edit_file.

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 usage for spreadsheet modification but does not explicitly state when to prefer this tool over alternatives like edit_file or write_file. No exclusions or alternative mentions are provided.

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