etsy_shop_shipping_profile_delete

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

The description simply says 'Delete', which is consistent with the destructiveHint annotation, but it adds no additional behavioral context beyond what the annotation already provides. It does not disclose any specific consequences or required permissions.

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, which is concise, but it lacks important details that could be included without excessive length. It is minimally adequate.

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 the tool has 2 required parameters and no output schema, the description is insufficient. It does not mention that the shipping profile must exist or any impact on associated data. The context provided by annotations and sibling tools partially compensates, but the description itself is too sparse.

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?

With 0% schema description coverage, the description does not explain the parameters (shop_id, shipping_profile_id) beyond their names. The agent must infer their meaning, which may be ambiguous without further context.

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 states the verb 'Delete' and the resource 'a shipping profile from a shop', which is specific and distinguishes it from sibling tools like create, get, list, and update for shipping profiles.

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 provides no guidance on when to use this tool versus alternatives, such as prerequisites or conditions for deletion. There is no mention of whether the profile must exist or any restrictions.

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