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

With no annotations provided, the description fully carries the behavioral burden. It discloses local execution with no external API dependency, returns only a numeric result rather than a breakdown, and explicitly states it does not fetch live market data. This is comprehensive transparency for a calculator tool.

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 well-structured, starting with core functionality, then output format, differentiation, usage guidance, and limitations. Every sentence contributes valuable information with no redundancy, and the longest part is justified by the need to distinguish from sibling tools.

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 absence of an output schema and annotations, the description provides sufficient context: supported calculation types, output nature, and relationship to sibling tools. It also clarifies the lack of live data, which is critical for correct tool selection. The description is complete for its complexity.

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 already provides 100% coverage, detailing each parameter and the accepted values for calculator_type. The description adds no additional parameter-level meaning beyond what the schema states, so the baseline of 3 is appropriate.

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 performs common financial calculations locally, lists supported calculation types, and emphasizes it returns a single numeric result. It explicitly distinguishes itself from financial_calculator by being the lightweight variant, making the purpose unmistakable.

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?

It provides explicit guidance: use this tool when only the headline figure is needed, prefer financial_calculator for full breakdowns, and use stock_quote, crypto_price, or currency_convert for live market data. This gives clear when-to-use and when-not-to-use instructions with named alternatives.

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