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

With no annotations, the description carries the full burden of behavioral disclosure. It transparently explains that the tool returns per-process estimates, sorts them by total cost, and provides a lowest-cost/shortest-lead-time note. It also flags the outputs as 'indicative and non-binding,' which is a critical behavioral caveat about the reliability and finality of the results. No contradictions exist.

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 two crisp sentences with zero filler. It front-loads the core purpose and immediately gives actionable instructions and expected output. Every sentence adds value, making it highly efficient.

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 no output schema, the description adequately explains the return format (per-process estimates sorted by total cost plus a note). However, it does not describe how optional parameters (material, finish, tolerance, bounding box) influence the estimates, which is a notable gap for a comparison tool where these inputs are likely important for accurate results. The description covers the core function but leaves feature-specific context under-explained.

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 has 0% description coverage, and the description only adds semantics for two of six parameters: 'processes' and 'quantity.' The optional parameters (finish, material, tolerance_mm, bounding_box_mm) are unexplained, leaving agents without guidance on how these affect the comparison. The description partially compensates but does not sufficiently cover the required schema gap.

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 verb 'compare' with a specific resource (cost and lead time across manufacturing processes) and scope (one part). It also lists the output (per-process estimates sorted by total cost) and explicitly differentiates from sibling tools like get_lead_time, which likely covers a single process, and estimate_bom.

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 usage instructions: 'Provide 2-8 process names and a quantity.' This tells the agent the necessary inputs and the range for the process list. It also implicitly distinguishes when to use (comparing multiple processes) and adds a caveat that it is 'indicative and non-binding,' guiding appropriate use. It lacks explicit alternatives, but the purpose makes the context clear.

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