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 the two-call validation flow, what step 1 returns (summary, consent line, token), that submission is only completed on step 2, and the downstream side effect that the person must click an emailed link before any provider sees the enquiry. It also spells out the consent scope (details shared with up to three providers, direct contact, per-firm notification, ability to stop).

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 purpose and clearly segmented into Step 1 and Step 2, so structure is strong. It loses a point because the full consent sentence is quoted verbatim, duplicating text already present in the consent parameter description in the schema.

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, and the description compensates by describing exactly what step 1 returns and what happens after step 2, along with the consent obligation. For a nested-object, two-phase submission 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 real meaning beyond it: answers are keyed by field key from the enquiry_fields tool, consent must be true in both steps, and confirmation is described as the token produced by step 1 and only sent after approval. The workflow binding of confirmation is not evident 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?

States a specific verb (submits) and resource (an enquiry to Cyber Essentials Cost) and explicitly disclaims what it is not ('NOT a purchase, NOT a guaranteed quote'). The two-step framing plus the 'human providers' scope distinguishes it clearly from the enquiry_fields/enquiry_describe siblings.

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 when-to-use conditions for each step: Step 1 'call with the answers... and consent=true', Step 2 'only if the person agrees', and names the prerequisite (confirmation token from step 1). It also specifies the gating action (show the summary and consent line) that must occur before step 2 is permissible.

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