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 that step 1 validates and returns a summary, consent line and token, that step 2 actually submits, and that the person must click an emailed link before any provider sees the enquiry. It also spells out what consent legally means.

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?

The critical constraints are front-loaded in the first clause, and the step-by-step structure is easy to follow. It is slightly long and repeats the consent sentence, which is 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?

For a two-step, side-effect-bearing tool with no annotations and no output schema, the description supplies everything needed: the return values of step 1, the side effect of step 2, and the double opt-in gate. Nothing material is left to inference.

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 the schema: it explains that answers must be keyed by field key from enquiry_fields and that confirmation is the token returned in step 1 and used only after the person approves the summary.

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 PPC agency Manchester) and immediately delimits scope with 'NOT a purchase, NOT a guaranteed quote,' which separates it from a booking/purchase action. The two-step framing makes its role distinct from the read-oriented siblings enquiry_describe and enquiry_fields.

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, sequenced when-to-use guidance: step 1 with answers and consent=true, step 2 only if the person agrees and with the confirmation token. It also names the precondition for step 2, so an agent knows exactly when each invocation is appropriate.

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