add_inventory

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

No annotations provided, so description bears full burden. It states 'real write' and auth requirement, but doesn't disclose failure modes, idempotency, or side effects beyond the write. Lacks complete 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, no filler. Front-loaded with essential purpose, then usage guidance. Every sentence adds value.

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 add-inventory tool with no output schema, the description covers core purpose, usage guidelines, and key trait (real write). Lacks return value info but is adequate for typical agent invocation.

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 description coverage is 0% per context, so description must compensate. Only mentions batch handling ('single-item array for one card') but does not explain inner fields like cardId, quantity, isFoil. Insufficient guidance for a 3-field object.

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 ('Add one or more cards to inventory') and differentiates from siblings by mentioning update_inventory and remove_inventory. It also explains the batch structure.

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?

Explicitly tells when to use alternatives: update_inventory for quantity changes, remove_inventory for deletions. Also notes auth requirement (IWMM_API_KEY) and emphasizes this is a real write.

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