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

With no annotations, the description carries the full disclosure burden and does so well: it reveals the two-phase confirmation gate, that step 1 returns a summary/consent line/token, that step 2 actually submits, and that an email double-opt-in link must be clicked before any provider sees the enquiry. This is exactly the kind of side-effect and consent-flow context an agent needs for a mutation tool.

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 constraint ('NOT a purchase') is front-loaded and the step sequence is easy to follow. It is somewhat dense and repeats consent=true, but nearly every clause carries procedural meaning, so the length is largely justified.

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 3-parameter mutation tool with no output schema, the description covers the full lifecycle: validation, return values, token reuse, actual submission, and the downstream email confirmation gate. Nothing an agent needs to call it 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 parameter shapes are already documented, giving a baseline of 3. The description goes further by explaining that answers are keyed by field key from enquiry_fields and that confirmation is only supplied on the second call after approval, adding sequencing semantics the schema cannot express.

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 human providers) and immediately disambiguates scope with 'NOT a purchase, NOT a guaranteed quote'. The two-step framing also distinguishes it from siblings like enquiry_fields (which supplies field keys) and enquiry_describe.

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 when-to-use sequence: Step 1 with answers+consent to validate and get a token, Step 2 only if the person agrees. It also states the preconditions (person has read/agreed to the consent line) and the exclusion that this is not a purchase, so an agent knows exactly when each call is appropriate.

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