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

With no annotations, the description carries the full burden and does disclose a key behavioral trait: 'One failure never aborts the batch,' indicating partial-failure isolation. It also mentions the 'max 100' limit. This is good but could further describe error reporting or output behavior, so not a 5.

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 three compact sentences, front-loading the purpose ('Run many calculations') and then covering the parameter structure and failure behavior without any fluff. Every sentence earns its place.

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?

The description covers the essential input contract and a key behavioral guarantee, but it omits what the response looks like (e.g., how results or errors are returned). Given the absence of an output schema and annotations, this is a minor gap for a batch tool, but it remains largely complete.

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 schema only says 'calls' is an array of objects, but the description specifies each element as '{tool, arguments}' and adds the limit of 100. This is crucial semantic detail that compensates for the 0% schema description coverage.

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 'Run many calculations in one request,' identifying the tool as a batch wrapper for calculation operations. This distinctively separates it from sibling tools like calculate_metric or currency_convert, which handle individual calculations.

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 'Run many calculations in one request' implies consolidation of multiple calculation calls, and the 'PAID FEATURE' label signals a cost consideration. However, it does not explicitly name alternatives or exclude single-call usage, so it lacks a 5-level explicitness.

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