Price a job

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

With no annotations, the description carries the burden. It explains the pricing components (rates, tax, deposit, profitability check) but does not disclose whether the tool has side effects (e.g., saving or caching). It implies read-only by saying 'Use this before creating any quote.'

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 concise at ~70 words, front-loads the purpose, and includes a critical usage instruction. It could be slightly more structured (e.g., bullet points), but it is efficient and readable.

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 explains inputs and the pricing logic well, but since there is no output schema, it fails to explicitly describe the return value (e.g., price breakdown, margin verdict). The mention of 'margin verdict' hints at output but does not confirm format.

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 100%, so baseline is 3. The description adds value by explaining how parameters drive the pricing engine (e.g., 'learned $/sqft rates by blast depth and surface', 'access factor'), enhancing understanding beyond the schema's 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?

The description clearly states 'Price an abrasive-blasting job' with a specific verb and resource, and distinguishes from siblings like 'quote_create' by adding 'Use this before creating any quote.'

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 provides a clear usage context ('Use this before creating any quote'), but does not explicitly exclude alternative tools like 'pricing_rates' or specify when not to use it.

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