available_serials

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

The description states the tool is read-only and provides a sample output format. With no annotations, it partially discloses behavior but lacks details on error handling, authentication, or how missing items are handled.

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 two concise sentences with no redundant information. The output format is front-loaded, and the use case is stated succinctly.

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 simple list tool with one parameter and no output schema, the description provides a clear output format and purpose. However, it lacks details on input format and error scenarios, making it minimally adequate.

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 schema has 0% description coverage, and the description does not explain the 'item_codes' parameter format or expected values beyond implying it accepts one or more codes. The description focuses on output, not input semantics.

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 it retrieves in-stock serial numbers and sell prices per firearm item, with a specific use case ('which units do we have of this model + at what price'). This distinguishes it from sibling tools like 'firearms_in_stock' or 'item_stock'.

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 includes a direct usage suggestion ('Use for...') and declares the tool as read-only, implying it is not for modifications. However, it does not explicitly exclude use cases or mention alternative tools.

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