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

With no annotations, the description carries the burden well: it discloses the two-call double-consent protocol, that step 1 only validates and returns a summary plus a token, that submission triggers a verification email the person must click before the vendor sees anything, and it quotes the exact consent wording. The remaining gap is failure behavior — invalid answers, a stale or mismatched confirmation token, or repeated submissions are not described.

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?

It is front-loaded with the most important framing (not a purchase) followed by the step sequence, and every sentence carries operational meaning. The exact consent sentence appears twice, once in prose and again in the schema, which is mild redundancy but defensible for a legal consent string.

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?

Although there is no output schema, the description explains what step 1 returns (a summary, the consent line, and a confirmation token) and what step 2 produces (submission plus a verification email). For a three-parameter, two-phase mutation tool this covers everything an agent needs to drive it 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 would be 3; the description earns more by explaining the relationship between parameters rather than restating them, notably that answers are keyed by field key from enquiry_fields and that confirmation is the token returned by step 1 after the person approves the summary. It adds workflow ordering that the schema alone does not.

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?

The description opens with a specific verb and resource ("Submits an enquiry to Outsourced IT Quotes") and immediately scopes it with two negations: "NOT a purchase, NOT a guaranteed quote." It also anchors the tool against its siblings by pointing to enquiry_fields as the source of the field keys, so an agent can tell this apart from the read-only enquiry_* tools.

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?

It gives an explicit procedural rule for when to call: step 1 with answers and consent, step 2 "only if the person agrees," plus the precondition that the summary and consent line must be shown first. What it doesn't do is state when not to use it (e.g. other enquiry paths) or how to recover from a failed validation or an expired confirmation token.

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