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

No annotations are provided, so the description carries the full disclosure burden. It thoroughly covers side effects: validation, summary/consent/token return, email receipt, and the emailed-link requirement before any provider sees the enquiry. It also quotes the exact consent text.

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 longer than average, but each part earns its place: disclaimers, ordered steps, consent semantics, and token role. The Step 1/Step 2 structure and front-loaded 'NOT a purchase' make it easy to parse for an agent.

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?

With no annotations and no output schema, the description supplies the necessary return values (summary, consent line, confirmation token) and post-conditions (email, provider visibility only after link click). The two-step contract gives an agent everything needed to invoke this tool correctly.

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 schema already covers 100% of parameter descriptions, so the baseline is 3. The description adds real semantic value by explaining answers are keyed by enquiry_fields field keys, that confirmation is the step-1 token used for the final submission, and that consent requires the quoted agreement text.

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 action ('Submits an enquiry to Class Q Checker') and immediately clarifies what it is not ('NOT a purchase, NOT a guaranteed quote'). It also distinguishes the two-step submission flow, making the tool's role clear against the related checker and enquiry 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?

The description gives explicit step-by-step when to call (Step 1 with answers/consent, Step 2 only after the person agrees and with the token) and an explicit when-not ('NOT a purchase'). It does not name a competing sibling tool to prefer in other cases, so it falls just short of full alternative routing.

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