add_inventory

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

States 'This is a real write', but does not elaborate on side effects (e.g., whether duplicates are allowed, if it overwrites existing rows). No annotations are provided, so the description carries the full burden; it is adequate but not thorough.

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 covering purpose, batch usage, alternative tools, and auth requirement. No filler, front-loaded with key info.

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?

Missing details on return value, idempotency, and error handling. For a write tool with no output schema or annotations, the description should clarify what happens after execution (e.g., success confirmation, added items).

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 'Accepts a batch - pass a single-item array for one card', which clarifies usage of the items parameter. However, the input schema already describes the nested properties with good detail. The description provides marginal added value 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 the action ('Add'), resource ('cards to inventory'), and scope ('authenticated user's inventory'). Specifies batch usage and distinguishes from sibling tools update_inventory and remove_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?

Explicitly tells when to use this tool (adding cards) and when to use alternatives (update_inventory for changes, remove_inventory for deletion). Also notes it is a real write and requires IWMM_API_KEY.

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