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 nothing is submitted on step 1, that a confirmation token is required for step 2, that an email verification click is required before any provider sees the enquiry, and it quotes the exact consent scope (up to three operators, name disclosure, opting out). These are non-obvious side effects and trust/consent requirements an agent could not infer.

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-loads the most decision-relevant fact (not a purchase) and organizes the rest as Step 1 / Step 2, which is easy to follow. However it is a long run-on block, and the full consent string is repeated verbatim from the consent parameter schema, which is redundant.

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 stateful two-call flow with a nested answers object, no output schema and no annotations, the description supplies everything needed: sequencing, what step 1 returns, the required token round-trip, and the downstream email verification. Nothing essential to invoking 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 the baseline is 3; the description goes further by tying 'answers' keys to the enquiry_fields sibling and by specifying that 'confirmation' is the step-1 token and is only supplied after the person approves the summary. The consent text is duplicated verbatim from the schema, adding no new meaning there.

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+resource ('Submits an enquiry to Ski Transfer Quotes') and immediately disambiguates what it is not ('NOT a purchase, NOT a guaranteed quote'). It also references the sibling tool enquiry_fields as the source of answer keys, so an agent can distinguish it from its siblings without opening a schema.

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 with conditions: step 1 validates and returns a summary/consent line/token, step 2 fires 'only if the person agrees'. The gate conditions (person must see the summary, must consent) are spelled out rather than implied.

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