import_buy_list

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

With no annotations provided, the description carries the behavioral burden. It discloses that the tool returns counts and per-row errors, which is helpful, but it does not mention idempotency, duplicate handling, or rate limits. The authentication requirement is noted.

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?

The description is concise: three sentences, no wasted words. It front-loads the main purpose, then provides format details and return behavior, making it easy to parse quickly.

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 single parameter with schema coverage, the description fully explains the input format and return value. The sibling context is rich with related buy-list and import tools, and the description is sufficient for an agent to understand the tool's role.

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?

The description adds significant meaning beyond the schema's parameter description by detailing the expected CSV header columns (name, set_code, number, etc.) and noting auto-detection of external formats. This clarifies formatting requirements beyond the schema's generic 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 tool bulk-adds cards to the user's buy-list from CSV text. It specifies the native format and mentions auto-detection of external exports, distinguishing it from siblings like 'add_buy_list' (single addition) and 'list_buy_list'.

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 explicitly requires 'IWMM_API_KEY' and describes the CSV format and auto-detection of external exports, indicating when to use it (bulk import). However, it does not explicitly contrast with siblings or state when not to use it.

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