excel_set_formulas

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds genuine value with the recalculation note ('request recalculation when opened in Excel'), clarifying that results are not computed server-side, but it omits the in-place mutation risk and overwrite behavior.

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?

A single tight sentence with no filler, and the core action is front-loaded. It is efficient, though the recalculation caveat slightly obscures rather than sharpens the main statement.

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 destructive 5-parameter mutation tool with no output schema and 40% schema coverage, the description is thin. It says nothing about whether existing formulas are replaced, how the optional cached 'result' interacts with recalculation, or what happens when outputPath is supplied.

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 only 40% and the description names no parameters at all. It never explains 'overwrite' (defaults to false), 'outputPath' (in-place vs. copy), or the optional 'result' field per formula, leaving the caller to guess at write semantics that directly affect data safety.

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 gives a specific verb and resource ('Set formulas in specific XLSX cells'), which is more precise than the generic write tools in the sibling set. It does not, however, explicitly contrast itself with excel_write_range or excel_native_batch, so the differentiation is implied rather than stated.

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?

There is no guidance on when to choose this tool over excel_write_range (which writes values) or excel_native_batch. No prerequisites, no exclusions, no alternative named — the agent must infer the boundary from the tool name alone.

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