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

With no annotations present, the description carries the full burden and delivers richly: it discloses that step 1 is non-committal validation, that step 2 triggers an email with a click-before-delivery gate, that providers see nothing until the link is clicked, and it quotes the exact consent language. This fully compensates for the missing annotations.

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 description is long but every sentence carries operational necessity: exclusions are front-loaded, steps are clearly labeled, and the verbatim consent line is essential for a compliance-sensitive tool. Slight redundancy exists in restating consent in both the consent parameter description context and the body, but overall it is dense rather than padded.

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 complex two-step mutation tool with no output schema and no annotations, the description is remarkably complete: it covers return values of step 1 in prose, the consent requirement, the post-submission email flow, and the prerequisite linkage to enquiry_fields. The only omissions, such as validation-failure behavior and token expiry, are minor and outside the core call sequence.

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 adds genuine workflow meaning beyond the schema by explaining which parameters belong to which step, that confirmation is the token returned from step 1, and that answers are keyed by field key from enquiry_fields. This exceeds baseline but stops short of fully documenting per-parameter edge cases.

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 plus resource — 'Submits an enquiry to Nearshore Finder' — and immediately sharpens the scope with 'NOT a purchase, NOT a guaranteed quote.' This distinguishes it clearly from the sibling compare_* and enquiry_* tools, so an agent can select it confidently.

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?

The two-step workflow is spelled out with explicit sequencing: call once with answers and consent=true to obtain a token, show the summary, then call again only if the person agrees. It also provides a hard condition for step 2 ('only if the person agrees') and routes the agent to enquiry_fields for the answer keying, which is effective alternative guidance.

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