import_inventory_cards

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

With empty annotations, the description carries full burden. It discloses that the tool mutates inventory (bulk-import), returns counts of saved/deleted/skipped rows and errors, and requires authentication. However, it omits details on rate limits, idempotency, or whether the import is reversible. Moderate transparency.

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 that efficiently cover purpose, input format, and output behavior without redundancy or fluff. Each sentence adds essential information, making it highly concise and well-structured.

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 the simple single-parameter input and no output schema, the description adequately covers all aspects: what it does, how to use it (input format), what it returns, and authentication requirement. No further information seems necessary for this tool.

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 100% with one parameter 'text', described as 'CSV text including a header row.' The description adds significant value by detailing supported header formats (native, Moxfield, etc.) and return data (counts and errors), going beyond the schema's minimal description.

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), the target resource (cards into the authenticated user's inventory), and the input method (pasted CSV text). It also specifies supported formats, making the tool's purpose unambiguous and distinguishing it from other import tools like import_buy_list or import_deck.

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) and implies bulk use, but does not explicitly state when to use this tool versus alternatives like add_inventory for single additions. However, the name and context make the usage clear enough.

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