delete_wishlist

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

No annotations are provided, but the description reveals the key behavioral trait: the confirm flag controls whether the operation is a dry-run or actual deletion. This adds important context that an agent needs to avoid accidental deletion.

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?

Two sentences with no redundancy. The first sentence states the purpose, and the second explains the confirm parameter. Both are front-loaded and essential.

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 no output schema and no annotations, the description covers the core behavior and parameter semantics. It does not describe the dry-run summary format or error conditions, but for a simple delete tool it is reasonably complete.

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 coverage is 0%, but the description explains the role of both parameters: id identifies the wishlist, and confirm switches between dry-run and actual deletion. This adds meaning beyond the schema's structural constraints.

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 action: delete a wishlist by ID. It distinguishes itself from sibling tools like delete_gift by specifying the resource (wishlist) and explains the dry-run vs actual deletion behavior.

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 explains the two-phase workflow: use without confirm for a dry-run summary, then with confirm to actually delete. This gives clear guidance on when to use each variant, though it does not explicitly mention alternatives.

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