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

No annotations are provided, so the description carries the full burden and does so: it discloses that step 1 only validates and returns a summary/consent line/token, that submission triggers an email with a link the person must click before any provider sees the data, and that details go to up to three suppliers who contact the person directly. It also quotes the exact consent text that consent=true attests to, which is essential for a tool that transmits personal data.

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 highest-risk caveat (not a purchase) and ordered to match the two-call workflow, so every sentence serves a purpose. It loses a point because the full consent sentence is reproduced verbatim in both the description and the schema's consent field description, which is redundant text an agent reads twice.

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 output schema, the description must explain returns and does: step 1 returns a summary, the consent line and a confirmation token. It also covers the post-submission lifecycle (email link, provider visibility) and the nested answers object's keying convention, leaving nothing material unstated for a 3-parameter, two-phase tool.

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 sequencing semantics the schema cannot convey: 'answers' are keyed by field key from enquiry_fields, consent must be true, and 'confirmation' is the step-1 token supplied only after the person approves the summary. The only shortfall is that the acceptable value types inside answers are left entirely to 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 Payroll Software Compare') and immediately disambiguates what it is not ('NOT a purchase, NOT a guaranteed quote'). Combined with the sibling set (enquiry_describe, enquiry_fields), an agent can tell this is the terminal submission action rather than the read-only discovery 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?

Gives an explicit two-step protocol: step 1 with answers + consent=true, step 2 only if the person agrees, re-calling with the same answers plus the confirmation token. It states the precondition (consent), the gate between calls (human approval of the summary), and the alternative to stopping (not calling step 2 at all).

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