get_stocks

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

No annotations exist, so the description carries the full burden. It implies a read-only operation ('current stock levels') but does not disclose whether data is real-time, cached, or if rate limits apply. It also does not describe the output format or behavior when 'skus' is omitted.

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, clear sentence with no unnecessary words. It is appropriately sized for a simple query tool.

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?

Although the tool is straightforward, it lacks return value details (no output schema) and fails to explain how results relate to other tools like 'get_fbw_stocks' or 'get_warehouses'. The description is too minimal for complete context.

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?

Both parameters have schema descriptions (100% coverage). The tool description adds minor value by reinforcing that omitting 'skus' returns all stocks, which is already in the schema. No extra semantics beyond schema are provided.

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 returns 'current FBS stock levels for a specific warehouse'. It uses a specific verb ('Get') and resource ('stock levels'), and distinguishes from sibling tools like 'get_fbw_stocks' (FBW vs FBS) and 'get_warehouses' (returns warehouse list, not stocks).

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 given on when to use this tool versus alternatives such as 'get_fbw_stocks' or inventory-related tools. The description does not mention when not to use it, prerequisites, or typical use cases.

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