Estimate the cost of running a process with the given inputs.

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating a safe read operation. The description adds no behavioral context beyond what annotations provide, such as whether the estimate is approximate, how it is calculated, or any side effects. Given annotations present, the description should add value but fails to do so.

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 that merely repeats the title. While short, it does not structure information effectively or earn its place—it is under-specified rather than concise. There is no additional context or organization.

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 3 parameters, a nested object, no output schema, and full schema description coverage of 0%, the description is highly incomplete. It provides no information about the return value, the meaning of 'cost', how to interpret the estimate, or any constraints. The description fails to make the tool usable.

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 has 3 parameters (x-api-key, inputs, process_id) with 0% schema description coverage. The description does not explain any parameter semantics—it doesn't describe what 'inputs' should contain, the format of 'process_id', or when 'x-api-key' is needed. The description fails entirely to compensate for the missing schema descriptions.

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?

Tautological: description restates name/title.

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 usage guidelines are provided. The description does not mention when to use this tool versus alternatives, such as when to prefer it over other estimate tools or actual order placement. There is no guidance on prerequisites or context.

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