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

No annotations exist, so the description carries the full burden and does so: it discloses validation behavior, that a summary/consent line/token are returned, that submission is a two-phase confirm-before-commit flow, and that the person must click an email link before any provider sees the data. Consent semantics are spelled out verbatim rather than left to the schema.

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?

Long but front-loaded with the disambiguation ('NOT a purchase') and then ordered by step, so every clause is operational. The consent sentence is duplicated from the schema description, which is the one piece of redundancy in an otherwise economical block.

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?

There is no output schema, and the description compensates by stating what each step returns (summary, consent line, confirmation token) and what the person ultimately receives (an email with a required click-through). For a nested-object, two-phase tool this is enough to invoke it 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 sequencing meaning: confirmation is only supplied on the second call and only after approval, and consent must be true in both steps. It doesn't explain answer key formats beyond pointing at enquiry_fields, but the procedural semantics are the valuable addition.

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?

Opens with a specific verb and resource ('Submits an enquiry to SIM Only Deals Compare') and immediately bounds it with what it is not ('NOT a purchase, NOT a guaranteed quote'). It also names the related tool enquiry_fields as the source of field keys, so an agent can separate it from the dataset_* siblings at a glance.

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 explicit preconditions and a condition for each call: step 1 with answers + consent, show the summary, step 2 'only if the person agrees' with the token. The gating condition for the second, irreversible call is stated, not inferred.

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