set_formula

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

Given no annotations, the description discloses key behavioral traits: formulas are stored but not calculated until the file is opened, and reading the cell returns the formula text. This goes beyond a basic description, though it could mention error handling or overwriting 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?

Two sentences, no wasted words. First sentence defines action, second provides critical behavioral context. Efficiently 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 adequate for basic use but lacks details on what happens if the cell already contains data, if the formula is invalid, or if the session is invalid. Sibling tools imply more context might be needed for error handling.

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 only adds meaning for the 'formula' parameter (example shows format, leading '=' optional). It does not clarify the 'cell' or 'session_id' parameters. This is insufficient.

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 an Excel formula to a single cell, with an example 'SUM(B2:B10)'. It distinguishes itself from related tools like write_cell (which writes values) and fill_formula (which fills a range).

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 by stating what the tool does, but does not explicitly guide when to use it over alternatives. For instance, it doesn't mention that write_cell should be used for writing constant values or that fill_formula is for ranges.

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