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

With no annotations, the description carries the full burden and discloses the complete flow: validation, return of a summary/consent line/token, the need for explicit person approval, the confirmation-token second call, and the required email click before providers see the enquiry. It also explains the exact consent meaning.

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 purpose and caveats, then clearly structured by steps. It is somewhat long and repeats the consent text already present in the schema, but the repetition supports the two-step contract and every sentence remains functional.

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?

Given the two-step workflow, nested answers object, lack of output schema, and no annotations, the description is complete enough for correct invocation. It covers inputs, sequencing, consent, and post-submission behavior without relying on missing structured fields.

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 parameters are documented in the schema. The description adds value by explaining that answers are keyed by enquiry_fields keys, that confirmation is the token from step 1, and that consent must be true in both steps.

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 specific verb ('Submits') and resource ('an enquiry to Send A Parcel Compare') and immediately distinguishes it from a purchase or guaranteed quote. It also names the sibling prerequisite implicitly by referring to field keys from enquiry_fields.

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 gives explicit two-step instructions with conditions: Step 1 with answers and consent=true, show the summary and consent line; Step 2 only if the person agrees, with the same answers, consent=true, and the confirmation token. It also clarifies what the tool is not (not a purchase, not a guaranteed quote).

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