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: it discloses that step 1 validates without submitting, that a confirmation token is returned, that the real submission happens only on step 2, and that the person must click an email link before any provider sees the enquiry. It also states exactly what consent means and warns that no quote is guaranteed.

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?

It is long, but front-loaded with the critical negative framing and structured as Step 1 / Step 2. The final verbatim consent sentence duplicates the schema wording, which is slightly redundant, but the rest of the content earns its length given the two-call protocol.

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?

No output schema exists, so the description compensates by describing what step 1 returns (summary, consent line, confirmation token) and what step 2 triggers (submission plus a verification email). For a stateful, consent-sensitive, two-call tool this is complete enough to invoke 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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: answers are keyed by field key from enquiry_fields, consent must be true only after agreement, and confirmation is the token returned from step 1 after approval. The sequencing rule for confirmation is real workflow semantics beyond the schema.

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 Structured Settlement Compare') and immediately disambiguates with 'NOT a purchase, NOT a guaranteed quote'. The two-step nature is spelled out, and it is clearly distinguishable from the enquiry_fields/enquiry_describe siblings it references.

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 when-to-use instructions: step 1 with answers and consent=true, then step 2 only if the person agrees and with the confirmation token. It names the alternative source for inputs (enquiry_fields) and states the gating condition (person must approve the summary) before the second call.

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