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

Annotations already signal side effects (readOnlyHint=false, idempotentHint=false), but the description adds crucial behavioral details beyond them: the tool performs email delivery itself, fails on missing/invalid customer email or Gmail send errors, and reveals the real carrier name on the bind page. It also explicitly disclaims texting capability, which is not inferable from 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?

Every sentence earns its place: the purpose is front-loaded, the usage guidance follows immediately, and the SMS warning is a single clear sentence. No redundancy; the description is efficient despite its length because each clause adds distinct, decision-relevant information.

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?

The tool has an output schema, so return values need no explanation. The description covers the side effect (email), failure conditions, the SMS prohibition, the differentiation from request_bind_inline, and the unique security property (carrier name revelation). An agent has everything needed to call it correctly and avoid promising a text.

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 description coverage is 100%, and both parameters have meaningful descriptions in the schema. The tool description merely restates the purpose of quote_id ('Quote whose saved customer email will receive the secure link') without adding new syntax or format details, so it stays at the baseline 3 for high schema coverage.

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 precise verb-resource pair: 'Generate a single-use secure link, valid for 7 days, and EMAIL it to the customer address already collected in the quote.' It also names the sibling request_bind_inline and draws a clear behavioral boundary ('does not text'), so an agent can distinguish this tool from the in-chat alternative without inspecting the 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?

The description explicitly states when to use this tool versus the sibling: 'prefer request_bind_inline for the in-chat flow. Use get_bind_link when the customer wants to leave the chat, finish on a different device, or receive their final numbers by email.' It also states a hard exclusion: 'Libertas customer texting/SMS is not enabled: this tool does not text and you must never promise a text message.'

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