remove_inventory

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

The annotations already indicate destructiveHint: true, so the description adds value by specifying the authentication requirement (IWMM_API_KEY) and the precise scope of removal (card+finish row). No contradiction with annotations.

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 extremely concise, using two short sentences with no redundant information. The key action and requirement are front-loaded.

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 no output schema, the description lacks information about return values or confirmation of successful deletion. It covers the core action and auth requirement but is minimal for a destructive operation.

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 little to explain the parameters beyond hinting that cardId identifies the card and isFoil determines the finish. It could explicitly state that cardId is a UUID and isFoil is a boolean for the finish type.

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 specific action ('Remove') and resource ('card+finish row from the authenticated user's inventory'), effectively distinguishing it from sibling tools like add_inventory or update_inventory.

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 the need for IWMM_API_KEY, implying authentication requirements, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., delete_transaction or remove_buy_list) or any precautions despite the destructive hint.

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