Delete payee

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

Annotations only declare readOnlyHint=false, which the word "Delete" already implies, so the description adds no context beyond the structured data. For a destructive operation it should disclose irreversibility, effects on related records or payments referencing the payee, and any auth requirements; none of this is present.

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?

It is a single short sentence with no wasted words, but the brevity reflects under-specification rather than efficient communication. There is no front-loaded detail to speak of beyond the verb and object.

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?

An output schema exists, so return values need not be explained, but for a destructive tool with only readOnlyHint=false in the annotations the description is too thin. An agent gets no signal about consequences, confirmation requirements, or side effects before invoking it.

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% for the single payeeUid parameter, so the schema already documents the input. The description adds no format or sourcing detail (e.g., where to obtain the UID), so the baseline 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 clear verb and resource ("Delete a payee"), so the basic operation is unambiguous. However, it is essentially a restatement of the tool name and title, and it does nothing to distinguish this from siblings like payee_create or payees_list.

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?

There is no guidance on when to use this tool versus alternatives such as payee_create, nor any mention of prerequisites or conditions. Nothing is misleading, but nothing is offered either.

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