remove_inventory

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

Indicates destructive action (remove) and a prerequisite, but lacks details on consequences (e.g., irreversibility, cascading effects) or what happens to associated data. With no annotations, the description carries full burden, yet it provides only basic info.

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?

Single sentence front-loading the core action and requirement. No extraneous words, perfectly concise.

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?

Adequate for a simple deletion tool but missing expected details about return values or success/failure indicators. With no output schema, some guidance on response would improve completeness.

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?

The term 'card+finish row' hints at the role of 'isFoil', but the description does not explain how 'cardId' or 'isFoil' are interpreted operationally. With 0% schema coverage, the description fails to compensate meaningfully.

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 (a card+finish row from the authenticated user's inventory). Differentiates from sibling tools like 'add_inventory' or 'update_inventory' by specifying removal.

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?

Provides an authorization requirement (IWMM_API_KEY) but no guidance on when to use this tool versus alternatives like 'delete_transaction' or 'update_inventory'. Missing context for selective usage.

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