Merchants Delete Merchant

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

Annotations already declare destructiveHint=true. The description adds vague terms like 'may delete, clear, reset' which could mislead about the operation's side effects. It fails to explain the key behavior of optionally moving data to another merchant via move_to_merchant_id, which is a critical behavioral trait beyond the annotations.

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 short but contains unnecessary vagueness in the second sentence. It is not front-loaded with the most important information (like the move-to option). While concise, it sacrifices clarity.

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?

With five parameters, no output schema, and a missing explanation of the move_to_merchant_id functionality, the description is incomplete. It does not prepare the agent for optional behaviors or return values, leaving significant gaps in understanding.

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 only 40%, and the description adds no additional meaning for any parameter. It does not mention the important move_to_merchant_id parameter, which allows reassigning data instead of deleting. The parameter descriptions in the schema are minimal, so the description should compensate but does not.

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 'Delete merchant' which is a clear verb+resource pair. However, the following phrase 'This may delete, clear, reset, or otherwise remove data' introduces ambiguity about the exact action, lowering the score from 5. It distinguishes well from sibling tools like get and update.

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 merchants_update_merchant or merchants_get_merchant. There is no mention of prerequisites, conditions for deletion, or the optional move_to_merchant_id parameter that affects usage.

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