Merchants Delete Merchant

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is known. The description adds little beyond a vague warning that data 'may delete, clear, reset, or otherwise remove,' which does not meaningfully clarify the specific behavioral consequences.

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 and front-loaded with 'Delete merchant,' but the second sentence is largely a tautological expansion that adds little concrete information. It is concise, but not every sentence earns its place.

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?

For a destructive operation with no output schema, the description should explain what happens to associated data, what move_to_merchant_id does, and what the return shapes mean. None of that is addressed, leaving an agent unprepared to invoke this safely.

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 description adds no parameter semantics. Schema coverage is only 50%, and the undocumented move_to_merchant_id parameter is significant and ambiguous, yet the description does not clarify whether it preserves or migrates data before deletion.

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 specific verb and resource: delete merchant. While the follow-up 'This may delete, clear, reset, or otherwise remove data' is vague, the name and first sentence are enough to distinguish it from sibling tools like merchants_update_merchant or merchants_get_merchant.

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 about when to use this tool versus alternatives, no mention of prerequisites, and no warning about what circumstances make deletion appropriate or what to do with related data. The description leaves all usage decisions to inference.

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