etsy_shipping_profile_upgrade_delete

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

While annotations already provide destructiveHint: true, the description merely repeats 'Delete' without adding details about what exactly gets destroyed, whether the operation is reversible, or what impact it has on the shipping profile.

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 with no extraneous information. It is concise and front-loaded with the core action.

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 and three undocumented parameters, the description is too sparse. It omits critical context such as required ownership, error conditions, or confirmation of deletion.

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 at 0%, so the description should elucidate the three parameters (shop_id, shipping_profile_id, upgrade_id). It does not define what a 'shipping upgrade' is or clarify that upgrade_id identifies a specific upgrade within a profile.

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 'Delete a shipping upgrade from a profile' uses a specific verb ('Delete') and clearly identifies the resource ('shipping upgrade') and context ('from a profile'). It distinguishes this tool from sibling tools like create, update, or list operations.

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?

The description lacks any guidance on when to use this tool versus alternatives such as create, update, or list. There is no mention of prerequisites, side effects, or conditions that would justify deletion.

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