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

With no annotations, the description carries full burden and excels: it discloses that submitting is not a purchase/guarantee, requires consent with exact wording, returns a confirmation token, triggers an email with a mandatory click before providers see it, and distinguishes step 1 from step 2. This gives the agent a clear behavioral model.

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 every sentence carries necessary procedural information, organized by step 1 and step 2. The front-loaded disclaimer ('NOT a purchase, NOT a guaranteed quote') prevents misuse early. Slight verbosity in the consent line is justified because it must be quoted exactly.

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 no output schema and no annotations, the description covers the entire call sequence including validation response, consent line, confirmation token, and email-link behavior. It lacks explicit error-handling guidance and the shape of step 2's response, but it is sufficient for correct invocation.

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 already describes all three parameters, but the description adds operational meaning: answers must be keyed by enquiry_fields keys, consent must be true and match the exact consent line, and confirmation is the token from step 1. This contextualizes the parameters beyond their schema definitions.

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?

Clearly states it submits an enquiry to Self Build Insurance Compare, explicitly distinguishing from a purchase or guaranteed quote. The title reinforces the action and step count, making it distinct from sibling comparison tools.

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 describes a precise two-step workflow: first call for validation and token, second call for actual submission only after agreement. It references enquiry_fields as the source of answer keys, guiding the agent toward the correct sibling for field definitions, though it doesn't explicitly list alternatives or when not to use it.

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