Stock Barcode Lookup Tool

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

No annotations exist, so this description is the only behavioral disclosure. It clearly signals a read-only lookup via 'Look up' and 'Returns the product name and quantity in stock,' and adds exact-match semantics. It doesn't describe not-found behavior, but the tool is simple, non-destructive, and its core behavior is transparent.

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 short sentences front-load the main purpose and returns, then note the sibling alternative. No filler or repeated schema content.

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 one-parameter lookup with an output schema, the description is complete: it specifies purpose, result, and the sibling alternative. An agent has enough context to invoke it correctly without needing more detail.

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%: the barcode parameter already has a clear type and example. The description only restates 'exact barcode' and adds no new semantic information beyond the schema.

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 states a specific action — 'Look up a product and its current stock level by exact barcode' — and names the exact resource and return scope. It also distinguishes from stock_search_tool by emphasizing exact barcode matching.

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?

It explicitly tells the agent when to use the tool: exact barcode searches. It also names an alternative and the condition that should route to it: 'For partial or name-based searches, use stock_search_tool instead.'

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