write_data

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

Annotations already give destructiveHint=true, indicating mutation. Description adds that it writes to cells and the mutual exclusivity of parameters, but does not detail whether it overwrites existing content or other behavioral nuances.

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 well-structured with a brief introductory sentence followed by a clear Args list. It is front-loaded and efficient, though it could be slightly more concise.

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?

Adequate for a write tool with destructiveHint, but lacks information about return values or error handling. Without an output schema, the agent does not know what to expect after writing (e.g., success flag, modified range).

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?

With 0% schema coverage, the description fully explains all five parameters: start_cell, data (2D list), formula (Excel formula), workbook, and sheet, including mutual exclusivity. This adds substantial meaning beyond the schema's type-only definitions.

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?

Clearly states 'Write data or a formula to Excel cells' with a specific verb and resource. Distinguishes between writing data (2D array) and a single-cell formula, and contrasts with sibling read_data.

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 clear instructions: use 'data' for a 2D array or 'formula' for a single-cell formula, and notes mutual exclusivity. However, does not explicitly advise when to use this tool versus alternatives like format_range or find_replace.

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