payments_delete_payment

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It communicates that deletion occurs, but does not state whether the deletion is permanent, reversible, cascading, or requires specific permissions. For a destructive operation, this is a meaningful gap.

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 extremely concise, one short sentence with no filler. While this is efficient, it provides only the bare minimum of value beyond the tool name, so it is not a fully robust description despite its compactness.

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 mutation with no annotations and no output schema, the description is incomplete. It does not mention consequences of deletion, return behavior, or any necessary safeguards. Given the simplicity of the single-parameter schema, more context about the deletion's impact was expected.

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%: the only parameter is `id`, described as 'Payment ID.' The description adds no additional parameter meaning, but the schema already provides sufficient semantic information, so the baseline score of 3 applies.

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: 'Delete a payment record.' This clearly distinguishes the tool from sibling operations like payments_create_payment, payments_update_payment, and payments_delete_prescription, which involve different actions or resources.

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 about when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or that updates should be preferred over deletion in certain contexts, so the agent must infer usage from the name alone.

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