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 this is not a purchase or guaranteed quote, what step 1 returns (summary, consent line, token), that step 2 triggers an email with a link the person must click before any provider sees the data, and that details go to up to three providers with opt-out rights. That is exactly the behavioral context an agent needs before mutating state.

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 crucial scope caveat and cleanly structured as Step 1 / Step 2. It is slightly long, largely because the full consent sentence is reproduced verbatim from the schema's consent description, which is mild redundancy though defensible since the agent must display it.

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 both the step-1 return payload and the step-2 downstream outcome (email plus click-through gate). Nothing needed to invoke either step 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 baseline is 3; the description goes beyond it by explaining that 'answers' must be keyed by field key from enquiry_fields and that 'confirmation' is the token returned by step 1 after approval, which is not stated in the schema field description.

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 Forklift Training Quotes') and immediately delimits scope with 'NOT a purchase, NOT a guaranteed quote'. It also cross-references the sibling enquiry_fields as the source of field keys, so an agent can place it among 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 the exact condition for each call: step 1 with answers plus consent=true, step 2 'only if the person agrees' with the confirmation token. The when-not condition is stated, not implied.

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