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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, but the description adds substantive behavior beyond them: contact details are never embedded in the link, prefill the form only, the link works without them, the privacy consent is never preselected, and the user must personally check and send the request. No rate limits or auth requirements are mentioned, hence not a 5.

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-loaded with what is returned, then privacy/prefill behavior, which is the right order. It is somewhat long and repeats the 'link works without them' idea that is also in the schema, but every sentence still carries operational meaning.

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?

With an output schema present, the description need not explain the return payload, and it covers the privacy and user-action semantics thoroughly. The gap is the absence of any relationship to the sibling quote/program tools, leaving the agent to infer whether this call presupposes a prior quote lookup.

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 goes beyond it by explaining how the optional 'contact' object is actually used (prefill only, never part of the link, only details the user chose to pass on) and noting the family is pre-filled on the page rather than recomputed. It adds real semantic value for the optional parameter.

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 states a specific verb and resource ('Returns only the personal link (quoteRequestUrl) for one programme and family') and the word 'only' scopes it against alternatives that would return amounts. It does not name the sibling tools (get_cbi_quote, list_cbi_programs) directly, so differentiation is implied rather than explicit.

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 describes the downstream workflow (the user opens the calculator page and sends the request personally) which implies when the tool fits, but it never states an explicit when-to-use or when-not-to-use condition relative to get_cbi_quote or list_cbi_programs. No prerequisites or ordering guidance are given.

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