etsy_shop_banner_delete

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

Annotations already indicate destructive behavior. The description adds minimal context beyond confirming the action. It doesn't describe side effects (e.g., reverting to default banner) or permission requirements. With destructiveHint present, description's burden is lower, but still lacks depth.

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 sentence that directly states the action. It is appropriately concise with no superfluous 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?

For a simple deletion operation, the description covers the basic purpose but leaves out parameter semantics and behavioral consequences. Given the low complexity, it is somewhat complete but could easily lead to confusion if shop_id format is unclear.

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 single parameter shop_id is not described. While its purpose may be inferred, the description does not confirm or provide any additional context (e.g., where to find the shop ID). Schema coverage is 0%, so description should supplement but fails to.

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 identifies the action (delete) and resource (banner image for a shop). It distinguishes itself from sibling tools like 'etsy_shop_banner_get' (retrieval) and 'etsy_shop_icon_delete' (icon deletion).

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 usage guidelines are provided. The description does not mention prerequisites, when to use this tool, or alternatives among sibling tools.

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