import_inventory_cards

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

No annotations provided, so description carries full burden. Discloses return values (counts, errors) and authentication requirement (IWMM_API_KEY). Lacks details on mutability, idempotency, or potential side effects like overwriting existing entries.

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?

Three sentences efficiently cover purpose, input format, and return values. Every sentence earns its place with no redundancy or fluff.

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 one parameter and no output schema, the description adequately covers key aspects: action, input specifics, returns, and auth. Minor gap: no mention of size limits or conflict resolution (e.g., duplicates).

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 provides 100% coverage with a description for the single 'text' parameter. Description enriches understanding by detailing supported headers and export formats beyond the basic 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 (bulk-import), resource (cards into inventory), and input format (pasted CSV text). It distinguishes from sibling import tools like import_buy_list and import_deck by specifying inventory cards.

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 specific format details (native header, auto-detected exports) that help users know when to use it. While it doesn't explicitly state when not to use it, the sibling tool list offers alternatives. Could be more explicit about selection criteria.

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