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

Annotations mark destructiveHint=true, and the description adds 'irreversible once sent', which is specific and useful. It also adds a payload restriction ('do not include medical details'), providing context beyond the annotation. No contradiction with 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?

Two sentences, front-loaded with the primary action, and no redundant words. The key warnings are included without fluff, making it highly concise and well-structured.

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 tool of this complexity (5 params, destructive annotation, output schema present), the description covers core behavior, payload limits, and irreversibility. Since an output schema exists, return values need not be explained. It lacks details about next steps but is otherwise sufficient for selection and invocation.

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 low (20% – only 'consent' has a description). The description mentions 'name and contact details', which loosely maps to name/email/phone but does not elaborate on each parameter or the preferred_language enum. The schema provides structural info but the description only partially compensates for the low 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 uses a specific verb ('Requests') and a clear resource ('callback from the clinic's patient coordination team'). It distinguishes itself from all sibling tools, which are read-only (get/fetch/search), and clarifies it collects only contact information, not medical details.

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 context is clear: this is the only mutating tool among read-only siblings, so usage is implied. The description adds a guideline about what to include ('only contact information') and explicitly excludes medical details, but it does not name alternative tools or state when not to use it.

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