Predict cost

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

With no annotations, the description carries the burden. It states 'Offline' and 'returns a cheapest-first ranking with assumptions', which hints at read-only and non-destructive behavior. However, it does not detail error handling, rate limits, or implications of 'assumptions'.

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?

Two concise sentences that front-load the action and outcome. Every word serves a purpose with no redundancy.

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 presence of an output schema and 10 parameters, the description is minimally complete but could better explain its relationship to sibling tools. It covers the core purpose and behavior sufficiently for an agent to select it.

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 coverage is high (80%), so baseline is 3. The description adds no extra meaning beyond the schema; it does not explain the role of key parameters like 'providers' or 'target'.

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's action ('forecast'), the resource ('cost of a prompt across candidate models'), and the output ('cheapest-first ranking'). It distinguishes itself from siblings like 'estimate_cost' and 'compare_models' by emphasizing it is done 'before the call' and is 'offline'.

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 description implies use before making a call but does not provide explicit guidance on when to use this tool versus alternatives such as 'estimate_cost' or 'select_optimal_model'. No exclusions or scenarios are mentioned.

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