list_formulas

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it lists formulas, without explicitly noting that it is a read-only operation, whether authentication is required, or if there are any side effects. For a tool with zero annotation coverage, this is a gap.

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, direct sentence that immediately conveys the core function. There is no fluff or repetition, and the key scoping detail ('current session') is front-loaded. It is appropriately concise for a simple list tool.

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 list operation with no parameters and no output schema, the description is adequate but minimal. It specifies the scope ('current session') and the resource, but does not describe the return format or any filtering options, which could leave an agent uncertain about the exact output structure.

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 tool has 0 parameters, and the schema coverage is 100% (trivially, since there are none). As per the baseline for 0 parameters, the description does not need to add parameter-specific details, and it meets this expectation without redundancy.

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 uses the specific verb 'list' and the resource 'calculation formulas' scoped to 'current session', which clearly identifies what the tool does. It is distinct from sibling tools like list_templates, list_components, and list_output_items, so an agent can differentiate it 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?

The phrase 'current session' provides a context cue, but there is no explicit guidance on when to use this tool versus alternatives like list_output_items or list_expression_functions. No exclusions or alternative suggestions are given, leaving usage partially implied.

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