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 well: it discloses that no provider sees the data until the person clicks an emailed link, that details may go to up to three suppliers chosen by the site, that the person can halt further distribution, and that validation errors surface in step 1. These are meaningful side effects an agent could not infer from 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?

Well front-loaded: the 'not a purchase/quote' caveat and the two steps come first, and the flow is scannable. The main inefficiency is the verbatim repetition of the long consent sentence already present in the schema's `consent` description.

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, yet the description tells the agent what step 1 returns (summary, consent line, confirmation token) and what to display to the person, and what step 2 triggers. Combined with the nested-object `answers` parameter, nothing needed to invoke this correctly is missing.

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. The description adds value beyond the schema by explaining the sequencing semantics of `confirmation` (a token produced by step 1, only used in step 2) and that `answers` must be keyed by field keys from enquiry_fields. It slightly over-repeats the consent text that is already in 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+resource ('Submits an enquiry to HACCP Software Compare') and immediately negates two likely misreadings: 'NOT a purchase, NOT a guaranteed quote'. This cleanly distinguishes it from the read-only compare_* and enquiry_* sibling tools, which gather criteria/options/fields rather than submitting anything.

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 an explicit two-step protocol: Step 1 with answers + consent=true to validate, and Step 2 only 'if the person agrees' with the confirmation token. It also names the gating condition (human approval of the summary) and references enquiry_fields as the source of answer keys, so the agent knows both when and how to call it.

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