Coda Get Formula

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

Annotations already cover safety (readOnlyHint, idempotentHint). The description adds genuinely useful context beyond them: the value is computed by Coda and reflects the latest state, and error state is surfaced. It doesn't mention auth scope or rate limits, but the added semantic context is solid.

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?

Front-loaded with the core action in sentence one, then returns and the alternative. The middle sentence enumerating return fields partly duplicates the output schema, so it is slightly less lean than it could be.

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 simple two-param read tool with an output schema and full annotations, the description covers purpose, returns, freshness, and the discovery alternative. Nothing an agent needs in order to call it correctly is missing.

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 100%, so the schema already documents both parameters. The phrase 'named formula' implies, but does not add new detail about, how formula_id_or_name resolves names — baseline 3 is correct when the schema does the heavy lifting.

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?

States a specific verb ('Get') and resource ('current value of a named formula in a Coda doc'), and explicitly distinguishes itself from the discovery sibling coda_list_formulas. An agent can tell it apart from coda_list_formulas and coda_get_control without opening a schema.

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?

Explicitly routes the agent to coda_list_formulas for discovery, which is the key usage decision here. It does not state when-not-to-use or cover edge cases (e.g., formula not found), so it falls short of a 5.

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