delete_payment_terms

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. The description only states the operation itself and does not mention whether deletion is permanent, irreversible, requires certain permissions, or affects associated records. This is a significant gap for a destructive tool.

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, concise phrase 'Delete payment terms' with no unnecessary words. It is front-loaded and to the point, perfectly sized for a simple delete operation.

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), the description is minimally viable but lacks any context about consequences, return values, or error conditions. Without annotations, the description does not fully address what an agent should expect behaviorally, though the operation itself is clear.

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 'id' parameter at 100% coverage with a clear description ('Payment Terms ID to delete'). The tool description adds no extra parameter information, but the schema already provides sufficient semantics, meeting the baseline for high schema 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 'Delete payment terms' uses a specific verb ('Delete') and a clear resource ('payment terms'), distinguishing it from sibling operations like get_payment_terms, create_payment_terms, and update_payment_terms. It unambiguously states the tool's function.

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 by the verb and resource: use when you need to remove a payment term. However, the description provides no explicit guidance on when to use this tool versus alternatives, and no mention of prerequisites or conditions (e.g., cannot delete if in use).

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