import_deck

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

Discloses return behavior (id + unresolved lines) and authentication requirement (IWMM_API_KEY). Without annotations, this provides useful behavioral context, though idempotency and side effects are not mentioned.

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 front-load the action and add key return info and requirement, no unnecessary words.

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?

Adequately covers input format, output, and requirement for a simple 3-param tool with no output schema. Missing explanation of format enum but schema covers that.

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%, but description adds an example for the 'text' parameter (one entry per line, e.g., '4 Lightning Bolt'), adding practical value beyond schema definitions.

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 tool creates a deck from pasted text, with specific input format and example. Distinguishes from siblings like create_deck (empty deck) and import_buy_list (different resource).

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?

Implies usage for bulk text import, mentions API key requirement, but no explicit guidance on when to use vs alternatives like create_deck or when not to use.

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