coda_get_formula

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

The description only indicates a read operation ('Get the value') but provides no additional behavioral context such as required permissions, side effects, error handling, or the nature of the returned value. Since annotations are absent, the description carries the full burden and is insufficient.

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 a single, concise sentence that is front-loaded and contains no unnecessary words. It is efficient but could include additional context without becoming verbose.

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 getter tool with two parameters and no output schema, the description is minimally adequate but lacks details about return value, error scenarios, and its relationship to other formula-related tools.

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?

The input schema includes descriptions for both parameters ('ID of the doc' and 'ID or name of the formula'), which covers the parameter semantics. The description adds no further value beyond what the schema already provides.

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 'Get the value of a specific formula' clearly states the action (get), the resource (formula), and its specificity (a specific formula). This distinguishes it from sibling tools like coda_list_formulas, which lists formulas, and other getters like coda_get_column.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that one needs to know the formula ID or name, nor does it contrast with coda_list_formulas or other retrieval tools.

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