set_inventory

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

With no annotations, the description reveals the key behavioral trait of overwriting the current available quantity. It does not disclose potential side effects, required permissions, or error handling, but for a simple set operation this is acceptable.

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 a single sentence that is direct and free of superfluous information. It front-loads the key action and result, making it easy to parse.

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 straightforward set operation with no nested objects or output schema, the description adequately covers the core functionality. It could mention error conditions or confirmation of the operation, but the current text is sufficient for an AI agent.

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?

All three parameters are fully described in the input schema, achieving 100% coverage. The description adds no additional parameter information beyond what the schema provides, 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 clearly states the tool sets inventory to an absolute quantity at a given location, using the verb 'Set' and resource 'inventory'. It distinguishes itself from the sibling tool 'adjust_inventory' by specifying it overwrites the current available quantity, implying a delta vs absolute operation.

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 explicitly notes that this tool overwrites the current quantity, indicating it should be used when a precise absolute quantity is needed rather than an incremental adjustment. However, it does not explicitly contrast with the sibling 'adjust_inventory' tool, leaving some ambiguity.

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