delete_payee

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

The description confirms the destructive hint from annotations and adds the requirement for confirmation, providing useful behavioral context beyond the annotation alone.

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 sentence with a brief annotation note, front-loading the key purpose and using no unnecessary words.

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?

While the description covers destructiveness and confirmation, it lacks information on return values, error handling, or prerequisites, which would be helpful given the absence of an output schema.

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?

With 0% schema description coverage, the description adds minimal parameter meaning: it mentions the need for confirmation but does not describe the 'id' parameter or clarify that 'confirm' must be true to proceed.

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 clearly states 'Delete a payee,' which is a specific verb and resource. It distinguishes itself from sibling delete tools by targeting payees exclusively.

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 explicitly notes the destructive nature and the need for confirmation, guiding the agent to use the confirm parameter. It does not mention alternatives, but the use case for deletion is clear.

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