remove_buy_list

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

Annotations already provide destructiveHint=true, indicating destructive nature. The description adds no further behavioral details beyond 'entirely' and auth requirement. For a destructive tool, this is adequate but minimal, as the annotations already cover the main behavioral trait.

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 that efficiently state the action, scope, and auth requirement. No unnecessary words or redundant information. Perfectly concise for a simple tool.

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 removal tool with only two parameters and no output schema, the description covers the essential context: what it does, what it affects (card+finish row), and auth needed. It could mention irreversibility, but destructiveHint already signals that. Slightly above average due to completeness for its simplicity.

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 for parameters is 100%, so the schema already describes each parameter. The description adds extra context that the row is identified by card+foil combination, which is helpful but not significantly beyond the schema descriptions. Baseline 3 is appropriate.

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?

Clearly states the action ('Remove') and the specific resource ('card+finish row from the authenticated user's buy-list entirely'). The verb 'remove' and resource 'buy-list' exactly match the tool's function and distinguish it from siblings like add_buy_list or update_buy_list.

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 mentions an authorization requirement ('Requires IWMM_API_KEY'), but does not provide explicit guidance on when to use this tool vs alternatives like update_buy_list or when not to use it. The usage context is implied by the purpose but not spelled out.

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