list_inventory

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

With no annotations, the description must disclose behavioral traits. It indicates a read-like operation (listing) and requires an API key, implying authentication. However, it does not explicitly state that it is read-only, nor does it mention rate limits, pagination constraints (e.g., max pages), or any side effects. Adequate but not fully informative.

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 concise sentences: first states the primary action and pagination, second covers return content and authentication requirement. No wasted words, front-loaded with purpose.

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?

The description covers the basics (what, return, auth) but lacks details on ordering, filtering, or default behavior. Given no output schema, it adequately describes the return shape but omits how pagination works (e.g., default page/limit) and whether the inventory includes all cards or just tradable ones. Sufficient for a simple list tool but could be richer.

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%: parameters 'page' and 'limit' have no description in the schema. The description only says 'paginated', which hints at page/limit usage but does not explain that 'page' is the page number starting at 1 or that 'limit' caps results. This adds minimal meaning beyond the raw schema.

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 ('list'), resource ('authenticated user's card inventory'), and outcome ('paginated', 'returns cards with quantities, prices, and metadata'). It effectively differentiates from sibling tools like 'export_inventory' and 'get_inventory_quantities' by specifying paginated listing with return details.

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 a prerequisite ('Requires IWMM_API_KEY') but provides no guidance on when to use this tool versus alternatives such as 'get_inventory_quantities' for just quantities or 'export_inventory' for bulk export. No exclusions or context hints are given.

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