update_inventory

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

Discloses that it replaces entire inventory and requires all products, which is a critical destructive behavior. No annotations provided, so description carries burden well, though it could detail side effects or errors.

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, front-loaded with purpose, no redundancy. Every sentence earns its place.

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?

Covers core replacement behavior and workflow, but leaves 3 undocumented parameters unexplained. No output schema, but description could be more complete given tool complexity.

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?

Adds value for products parameter (must be full list), but ignores sku_on_property, price_on_property, quantity_on_property. With only 20% schema coverage, description should compensate more.

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?

Explicitly states it updates the full inventory for a listing, using specific verb and resource. Distinguishes from siblings like update_listing by specifying inventory replacement.

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?

Provides clear workflow: retrieve current state via get_inventory, modify locally, then call with full list. Implies it's a replacement, not partial update, but doesn't explicitly exclude alternatives.

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