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

With no annotations, the description carries the full burden and discharges most of it: it discloses the two-phase flow, that step 1 only validates and returns a summary/token, that details go to up to three providers, and that an email link must be clicked before any provider sees the enquiry. It does not cover failure modes, token expiry, or what happens on duplicate submission, which is why it stops short of 5.

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?

Front-loaded and organized as a numbered step flow, with the critical 'not a purchase' caveat up front. It is verbose, and the full consent string is reproduced verbatim even though the schema already contains it, but that repetition is arguably functional since the agent must show the consent line to the person.

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 consent-gated, two-step mutation with no output schema, the description covers the flow, the consent semantics, the privacy consequences, and the email-verification gate. An agent has everything needed to call both steps correctly and to explain the outcome to the person.

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 and the description mostly restates the schema's own documentation of answers, consent, and confirmation. It adds only the sequencing nuance that the confirmation token comes from step 1 after approval, which the schema already implies. No enum or format detail is added.

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 (submits) and resource (enquiry to human providers) and explicitly distinguishes itself from the sibling calculate tool with 'NOT a purchase, NOT a guaranteed quote'. An agent can tell this is a consent-gated enquiry submission, not a calculation or purchase, without opening any schema.

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 two-step protocol: call with answers and consent=true first, show the person the summary and consent line, then only call again with the confirmation token 'if the person agrees'. It even names the sibling enquiry_fields as the source of the field keys, so the sequencing and the alternative are fully specified.

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