set_inventory

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

With no annotations, the description carries the full burden of behavioral disclosure, but it provides none. It does not state whether the operation overwrites existing quantity, requires special permissions, is reversible, or what the response contains. The verb 'set' implies mutation but adds no safety or side-effect context.

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 extremely concise at four words, front-loaded with the action and resource. However, it is so sparse that it sacrifices meaningful context, though every word does contribute to a basic understanding of the operation.

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 mutation tool with three required parameters and no annotations or output schema, the description is incomplete. It lacks information about return values, side effects, error conditions, and how it differs from the sibling 'adjust_inventory'. The minimal description does not adequately support an agent in invoking the tool correctly.

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 100%, with each parameter ('inventoryItemId', 'locationId', 'quantity') having a basic description. The tool description adds no additional parameter semantics beyond the schema, so the baseline score of 3 is appropriate.

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 'Set on-hand inventory quantity' uses a specific verb ('Set') and identifies the resource ('on-hand inventory quantity'). It distinguishes from sibling 'adjust_inventory' by implying an absolute overwrite rather than an adjustment, though it doesn't explicitly state the distinction or mention the required item/location context.

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?

No guidance is provided on when to use this tool versus alternatives like 'adjust_inventory' or 'get_inventory'. There is no mention of prerequisites, typical scenarios, or exclusion criteria, leaving the agent to infer usage from the name alone.

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