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

With no annotations, the description carries the full burden and does so richly: it discloses the two-step validate-then-submit flow, that step 1 returns a summary/consent line/token that must be shown to the person, that submission triggers an email requiring a click before any provider sees the data, and the exact downstream fan-out to up to three contractors. These are real side effects an agent could not infer from the 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?

The critical disclaimers ('NOT a purchase') are front-loaded and the two steps are ordered logically. It is long, and the consent text is essentially duplicated from the schema, but that repetition is justified because the agent must display the consent line verbatim to the user.

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 multi-step, no-output-schema, nested-object tool this is complete: it explains what step 1 returns, what the token is for, when to proceed to step 2, and the downstream consequences of consent. Nothing needed to invoke it correctly 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 the baseline is 3; the description adds flow-level meaning by tying 'answers' to field keys from enquiry_fields and by sequencing the confirmation token between step 1 and step 2. It does not add value-type or format constraints beyond the schema, so it stops short of a 5.

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 an enquiry to Duct Cleaning Quotes') and immediately scopes it against the two most likely misreadings ('NOT a purchase, NOT a guaranteed quote'). It also cross-references the sibling enquiry_fields as the source of answer keys, so an agent can distinguish it from enquiry_describe and enquiry_fields without opening schemas.

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 explicit, conditional when-to-call rules for both invocations: step 1 with answers + consent=true; step 2 'only if the person agrees' with the same answers plus the confirmation token. The gating condition (human approval) is spelled out rather than implied.

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