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

Goes well beyond the annotations: discloses that Haulest is a lead desk rather than a carrier, that calls may arrive within minutes in the US/UK, that each call creates one request, and that same phone/email within a day is de-duplicated. It also states the return shape ('a request reference and what happens next'), which matters because there is no output schema.

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?

Six tight sentences, front-loaded with the action and the lead-desk mechanism, then the consent gate, then dedup behavior, then the return. Every sentence carries a distinct fact an agent needs; nothing is filler.

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 15-parameter mutation with no output schema, the description covers what the tool does, the hard consent prerequisite, third-party contact timing, idempotency-like dedup behavior, and the shape of the response. Nothing material is missing.

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 all 15 parameters are already documented in the schema. The description restates the consent requirement and the name/phone/email gate but adds no syntax or format detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource ('Submits a quote request to Haulest') and immediately defines the mechanism: licensed movers call/email the person with written estimates. This is clearly distinguishable from siblings like find_movers or estimate_moving_cost, which don't create a lead-desk request.

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?

Gives an explicit precondition gate ('Call this only after the person has given their name, phone, and email for this purpose and has explicitly agreed to be contacted') plus a confirmation step before calling. No sibling alternative is named for cases where consent isn't given, so it stops short of the full when/when-not/alternatives pattern.

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