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

Annotations declare a write, open-world, non-idempotent call; the description adds real context the annotations cannot: the request is emailed to sales@gixfiber.com and triggers human follow-up, optional fields control whether routes/pricing come back, and test=true means logged-but-never-emailed. It does not warn that resubmitting creates duplicate leads (non-idempotent), which would be the final missing piece.

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 opening 'More detail is available' is filler, and the ask for company/role/need/contact email duplicates the earlier sentence about answering a few questions. The information is all relevant, but it is repeated rather than front-loaded into a tight, scannable statement.

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 14-parameter, non-idempotent write tool with no output schema, the description does cover the return (route options and a quote range) and the external email side effect. It leaves out which fields are required, duplicate-submission behavior, and any rate/abuse limits, so it is adequate but not complete.

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% and each field already documents its purpose and payoff, so the schema carries the burden. The description's enumeration (company, locations, use case, capacity, timeline) and its 'route options and a quote range' framing restate that, adding only light reinforcement that optional fields improve the response.

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 the concrete action: submit a quote request describing the user's company, locations, use case, capacity and timeline, and receive route options plus a quote range. That is a specific verb+resource an agent can match to intent. It never names a sibling, though the opening 'More detail is available' implicitly positions it as the deeper step beyond get_network_info without saying so.

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?

Use is implied (when the user wants routes, latency and pricing guidance) and 'More detail is available' hints at an escalation path, but there is no explicit when-to-use versus siblings like get_network_info or list_resources, and no stated exclusions for when not to submit.

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