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

The description says the tool only prepares a request and that 'Nothing is filed or emailed until confirm is called', which frames this invocation as non-filing and non-destructive. The annotations declare destructiveHint=true, directly conflicting with that stated behavior. The other rich context about auth and hand pricing does not resolve this annotation contradiction.

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 front-loaded with the core purpose and then adds the critical two-step workflow and auth prerequisite. It is dense but mostly earns its length, with only a long parenthetical input list making it slightly heavy.

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?

For a nine-parameter tool with an output schema, the description covers the essential agent-facing context: what it returns, that nothing is filed until confirm, the signed-in requirement, and that Printdash prices manually afterward. The only serious issue is the annotation mismatch, not missing workflow information.

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 parenthetical list enumerates all nine inputs, including mapping address_id to delivery address and similar_product_id to a similar catalogue product. This compensates for only 56% schema description coverage, though it adds little detail beyond the parameter names for fields like sides, stock, and quantities.

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 states a precise verb and resource: it prepares a custom quote request for jobs the catalogue does not cover. It distinguishes this from ordinary catalogue pricing and from the later confirm step, so an agent can recognize the tool without checking siblings.

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 clearly explains when to use the tool: for jobs outside the catalogue, after collecting customer details, and before calling confirm once the customer agrees. It also states the signed-in account prerequisite. It does not explicitly name a sibling alternative such as price_job for catalogue-covered work, so it falls short of a full 5.

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