excel_write_range

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

No annotations provided. Description does not explain that this is a destructive write operation, what 'patches' means, or that it requires an approval_id. No mention of side effects, rate limits, or error conditions.

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?

Description is a single 8-word sentence that is too terse to be helpful. It lacks structure and key information like what the tool actually does.

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 description does not mention what the tool returns. For a complex write operation with 6 required parameters, the description is severely incomplete.

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?

Zero schema description coverage. Description gives no details on any of the 6 parameters. 'rectangular value matrix' hints at values being 2D, but start_cell, sheet, doc_id, revision_id, and approval_id are unexplained.

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?

Description mentions creating patches for a rectangular value matrix, but 'excel_set_cell patches' is jargon and not immediately clear it writes to an Excel range. Sibling tools like excel_read_range suggest read/write distinction, but the purpose is not explicitly stated as writing values to a sheet.

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 such as excel_read_range or document_propose_edit. No context on prerequisites or typical use cases.

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