set_formula

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

With no annotations available, the description carries the full behavioral burden and does so extensively. It discloses formula normalization, #NAME? avoidance, recalculation flagging, stale cached results, the recalculate tool dependency, auto-backup behavior, atomic verified save, and refusal while Excel has the file open. This is unusually transparent.

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?

The description is dense but every sentence earns its place: core behavior, normalization/recalculation consequences, backup/atomicity, and an important constraint are all covered with no filler. The most important distinguishing behavior is front-loaded.

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?

The description is remarkably complete for behavioral context, covering side effects, safety, and recalc implications. It loses a point because several parameters remain under-documented given the 0% schema description coverage, and it does not explicitly route to sibling tools for non-formula writes. Overall, it gives an agent enough to operate safely.

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 0%, so the description must compensate for undocumented parameters. It adds meaningful context about 'formula' and 'location' by describing single-cell versus range-fill behavior, and indirectly explains 'backup'. However, key parameters like path, sheet, allow_loss, verify_com, and the exact location format are left unexplained, leaving a significant gap.

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 states a specific verb ('Write a formula') and resource ('a single cell, or fill a range'), and clarifies the exact Excel-copy semantics with relative reference shifting and absolute anchors. This clearly differentiates it from siblings like set_cell, write_range, or apply_edits.

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 makes it clear when to use the tool: when writing formulas to a cell or filling a range with formula semantics. However, it does not explicitly mention alternatives, such as using set_cell for plain values or write_range for non-formula data, nor does it state when not to use this tool beyond the Excel-open refusal.

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