update_payee

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

Annotations already indicate mutability (readOnlyHint=false) and destructiveness (destructiveHint=true). The description only adds '[mutating]', which is redundant and adds no new behavioral context such as what gets destroyed or any side effects.

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 very short (6 words) and front-loaded with the verb. However, it is too minimal to be considered well-structured for a complete tool definition. Every word is accounted for, but crucial information is missing.

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 no output schema and missing parameter descriptions, the description is incomplete for a mutation tool with destructive hint. It does not specify update behavior (partial vs full replacement), constraints (e.g., payee must exist), or error conditions.

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 0% with no parameter descriptions. The description does not explain the meaning of id, name, or category, nor does it clarify which are required beyond the schema's required list. The agent gains no additional insight.

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 'Update a payee', which clearly identifies the action and resource. It distinguishes from sibling tools like create_payee, delete_payee, and other update tools. However, it lacks details on what fields can be updated beyond the schema.

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 on when to use this tool vs alternatives like create_payee or delete_payee. The description does not mention prerequisites, when updates are appropriate, or when to avoid using it.

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