payments_delete_prescription

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

No annotations are provided, so the description carries the full burden. It signals destructive intent with 'Delete' and 'remove', but it does not disclose that deleting the prescription also removes all persons and payments, nor does it mention irreversibility or other side effects.

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 description is a single sentence with no filler. It front-loads the primary action and states the secondary mode efficiently, earning every word.

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 destructive, dual-mode tool with no annotations and no output schema, this definition is too thin. It omits side effects, sibling differentiation, and operational context, leaving the agent to infer important safety and routing information.

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%: each parameter has a meaningful description, including the important note that delete_prescription 'deletes the entire prescription with all persons and payments'. The tool description adds no parameter-level detail, but the schema already covers that burden.

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 names the resource ('payment prescription') and both supported actions ('Delete' / 'remove persons'), so an agent can tell what the tool does. It does not explicitly distinguish it from siblings such as payments_delete_payment or payments_update_prescription, so it falls just short of a 5.

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 offers no guidance on when to use this tool versus related tools like payments_delete_payment or payments_update_prescription. The dual mode is implied by the wording, but there is no decision rule, prerequisite, or alternative comparison.

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