get_formula

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

No annotations are given, so the description must cover behavioral traits. It implies a read operation by stating 'Get details', but does not explicitly confirm it is read-only or non-destructive. It also does not mention error behaviors or permissions. The description is adequate but lacks explicit transparency.

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 sentence with no unnecessary words. However, it could be slightly expanded to include parameter hints without losing conciseness. It is well-structured and front-loaded with the key purpose.

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?

Given the tool has an output schema and only two parameters, the description provides the core idea but misses context like parameter clarification and usage scenarios. It does not fully compensate for the lack of schema descriptions or annotations, but is minimally complete for a simple retrieval tool.

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%, meaning the input schema provides no parameter descriptions. The tool description does not explain what 'doc_id' or 'formula_id_or_name' represent, forcing the agent to infer from the tool name. This is insufficient for a tool with two required parameters.

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 retrieves details about a specific named formula, including its computed value. It uses a specific verb 'get' and resource 'formula', and distinguishes from sibling 'list_formulas' by indicating it targets a specific formula by name or ID.

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 like 'list_formulas'. There is no mention of prerequisites, context, or scenarios where this tool is appropriate or inappropriate.

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