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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds material context beyond them: the link opens only an intake page, no case is created, no records are transmitted, and the patient personally confirms consent. This correctly warns the agent that calling the tool has no data-side effects, which is exactly the behavioral detail needed here.

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?

Three sentences, front-loaded with what the tool returns, then the privacy/consent caveats. Dense and nearly waste-free, though the final sentence partially restates the earlier 'no records are sent' point from an input rather than output angle.

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?

An output schema exists, so return format needn't be described. The description covers the read-only nature, consent flow, and intake-only behavior, which is enough for a zero-required-parameter link generator. It could still note link delivery or expiry, but nothing critical is missing.

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 67%, so most parameters are self-documented. The description adds a useful negative constraint ('accepts no names, contact details or records') that shapes how the question field should be filled, but it says nothing about cancer_type or the preferred_destinations enum values, leaving those entirely to the schema.

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: it returns a link that lets a patient start an expert review by named organizations, enumerating what the review covers (records, options, trial shortlist, next step). That is unambiguous and clearly distinct from siblings like find_clinical_trials or send_feedback, though it never names an alternative tool to route to.

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?

Usage is implied rather than stated: the patient wants an expert review, so the agent calls this. There is no explicit when-to-use/when-not guidance and no comparison against ask_opencancer or find_clinical_trials, which an agent could plausibly confuse with this workflow.

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