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 validation behavior, the returned summary/consent line/token, the double-submit consent gate, and the post-submit email-confirmation step that gates provider visibility. It omits edge behavior such as what happens on failed validation or token expiry, which keeps it short of a 5.

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?

Front-loaded with the disqualifying caveat, then the two steps in order — a good structure for an agent reading top-down. The consent sentence is duplicated verbatim from the schema's consent description, which is the one redundancy keeping it off a 5.

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 must explain returns, and it does: step 1's summary, consent line and token, and step 2's submission plus the confirmation email with its click-to-reveal link. Combined with the nested answers object being tied back to enquiry_fields, an agent has everything needed to call both steps 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 description coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains the answers object is keyed by field key sourced from the enquiry_fields sibling, and that confirmation is the step-1 token echoed back only after approval. That sequencing context is not derivable from the schema alone.

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?

The description gives a specific verb+resource (submits an enquiry to a named provider) and immediately scopes it against the most likely misreading — 'NOT a purchase, NOT a guaranteed quote'. It also names the sibling source of the field keys (enquiry_fields), so the agent can distinguish it from the adjacent 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?

It lays out an explicit two-step protocol with the exact condition gating each call: step 1 validates and returns a token, step 2 runs 'only if the person agrees' with the same answers plus the token. The when-not is stated too (not a purchase, not a quote), leaving nothing to inference.

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