delete_payment

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

With no annotations, the description must fully disclose behavior. It only states 'Delete a payment,' implying a destructive action but omitting critical details such as whether the deletion is permanent, cascading effects, authorization needs, or constraints on payment status. The minimal information is not sufficient for safe invocation.

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 at three words, which avoids verbosity. However, it lacks structure such as front-loading key constraints or implications. For a simple tool, the brevity is acceptable but could benefit from slightly more structure.

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?

Given the tool's simplicity (one parameter, no output schema, no annotations), the description is minimally complete but fails to provide essential context like deletion behavior, irreversibility, and any required prior conditions. An agent would be under-informed to use this tool safely.

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?

The schema covers the single parameter with a description 'Payment ID to delete,' achieving 100% coverage. The tool description adds no additional semantic value beyond what the schema already provides, so the baseline score of 3 is appropriate.

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 'Delete a payment' is a clear verb+resource combination that distinguishes this tool from sibling delete tools for other entities (e.g., delete_contact, delete_product). However, it is essentially a tautology of the tool name and does not add specificity about what deletion entails (e.g., irreversible, soft delete, scope).

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?

No guidance is provided on when to use this tool versus alternatives like update_payment or other deletion tools. There is no mention of prerequisites, when not to use, or potential consequences, leaving the agent without decision-making support.

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