import_inventory_cards

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

No annotations provided. Description mentions requires API key and return counts, but lacks details on mutation behavior, idempotency, error handling, or rate limits. For a write tool, this is insufficient.

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 covering purpose, method, output, and requirements. No redundant information.

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?

For a simple tool with one parameter and no output schema, the description covers input format, output summary, and authentication. Lacks mention of delimiter or max text size, but overall adequate.

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?

Single parameter 'text' with schema description. Description adds value by detailing native header format and auto-detection of common export formats, which goes beyond the 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?

Description clearly states verb (Bulk-import), resource (cards into inventory), and method (CSV text). Also lists supported formats, distinguishing it from siblings like add_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?

Context implies use for bulk CSV import. However, it does not explicitly contrast with add_inventory (single card) or import_buy_list (buy list). Missing explicit when-not-to-use guidance.

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