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

With no annotations provided, the description carries the full behavioral burden and does so: it discloses that step 1 only validates and returns a summary/consent line/token, that step 2 actually submits, that contact details go to up to three named UK fabricators, and that an email link must be clicked before any provider sees the enquiry. These side effects and the consent requirement are exactly what an agent needs and cannot get from the schema.

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 purpose and the not-a-purchase caveat, then walks the two steps in order, so it reads well. It is long and re-quotes the full consent sentence verbatim from the schema, which is redundant, though arguably justified since the agent must show that exact line to the person.

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 what step 1 returns (summary, consent line, confirmation token) and what step 2 triggers (submission plus a verification email). Combined with the consent semantics, an agent has everything needed to drive the flow 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: answers must be keyed by the field keys from enquiry_fields, consent must be true in both calls, and confirmation is only supplied on the second call after approval. It also explains that the token originates from step 1's response, which the schema does not convey.

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 Metal Fabrication Quotes) and immediately bounds what it is NOT: a purchase or a guaranteed quote. It also distinguishes itself from the sibling enquiry_fields by naming it as the source of the field keys used in the answers object.

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: Step 1 call with answers + consent=true to validate and obtain a token, Step 2 call again only after the person agrees. The gating condition for the second call and the 'not a purchase' caveat leave nothing to inference.

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