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

Annotations already declare non-readOnly, non-idempotent, non-destructive, and openWorld. The description adds meaningful behavioral context beyond annotations: it is for human pricing (implying manual review and delay) and it must only be called after explicit customer agreement. These are additional behavioral traits that help an agent anticipate side effects and prerequisites. No contradiction with annotations.

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 sentences, with the core purpose front-loaded and the usage condition following succinctly. Every sentence adds value: the first establishes the tool's action, the second the critical precondition. No redundancy or filler, making it optimally concise for an agent to parse.

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 tool has 18 parameters and 7 required, but an output schema exists, so return values are documented elsewhere. The description covers the essential action ('submit enquiry for human pricing') and the critical precondition (customer agreement). It does not explicitly state that submission is a long-running process or how to track it, but 'human pricing' implies manual handling, and the output schema likely covers the response. Given complexity and existing schema, the description is sufficiently complete for correct invocation.

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 description coverage is 100%, so the schema already documents all 18 parameters, including required ones. The description adds no parameter-specific meaning beyond what the schema provides. Per the rubric, a baseline of 3 is appropriate when the schema does the heavy lifting; the description's general context does not enhance parameter understanding.

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 uses a specific verb ('Submit') and resource ('structured titanium material enquiry') and adds the purpose 'for human pricing'. This clearly distinguishes it from the generic sibling 'request_quote' and the status-checking 'get_quote_status'. The description is not a tautology and immediately conveys what the tool does.

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 gives an explicit precondition: 'Only call after the customer has reviewed the interpreted requirement and explicitly agreed to submit it.' This is a clear when-to-use directive. It does not explicitly mention alternatives (e.g., when to prefer request_quote), but the context of titanium and human pricing implies selection. The condition is sufficiently explicit to guide correct usage.

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