set_inventory_level

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

No annotations are provided, so the description carries the full behavioral disclosure burden. 'Set' implies a state-changing write operation, which is reasonably clear, but it doesn't describe effects like whether overrides are absolute or additive, whether there are validation constraints (e.g., negative quantities rejected), or whether changes are reversible. It's a mutation tool with no annotation coverage, so more context would be valuable.

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 sentences, efficient and front-loaded with the core purpose first. The second sentence provides useful pointer context. No wasted 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?

For a 3-parameter, all-required mutation tool with no annotations and no output schema, the description is adequate but thin. It tells the agent what the tool does and how to find required IDs, but says nothing about the return value, error cases, or semantic behavior of stocked_quantity (absolute set vs. delta). Given the tool's simplicity, a 3 is fair but borderline.

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%, and the description does not explain any of the three parameters beyond their schema types. Nothing clarifies what stocked_quantity means (units? whether it's an absolute overwrite?), or what format location_id and inventory_item_id take. With zero coverage, the description should compensate but doesn't.

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 uses a specific verb ('Set') with a clear resource ('stocked quantity for an inventory item at a stock location'), which clearly distinguishes it from the sibling read tools like list_inventory_items. It's clear but doesn't explicitly contrast with siblings beyond the reading tools.

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 names sibling tools list_inventory_items and get_store_context as prerequisites for finding the required IDs. This provides helpful context on how to gather inputs, though it doesn't explicitly say when NOT to use this tool or contrast it with other mutation tools.

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