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

The throttling disclosure (5/min) is genuinely valuable and is not derivable from the annotations, which only cover read-only/non-destructive behavior. The raw endpoint path also aids debugging. It does not warn about the paged-window result shape, which is the main behavioral surprise for callers.

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?

Four short sentences, front-loaded with the resource and scope, with the critical throttling warning before the endpoint. The telegraphic noun-phrase opener is slightly elliptical but wastes nothing.

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 7-parameter read tool with no output schema, the description never indicates what a result entry looks like (SKU plus per-warehouse quantity fields) or how the paged window behaves across calls. Pagination is covered by the schema, but the response shape is undocumented anywhere.

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 coverage is 100%: pagination fields, page_size defaults, and the warehouse_id origin are all already documented in the schema. The description only repeats the warehouse_id lookup hint, adding no syntax or format detail beyond what structured data provides, so the baseline 3 applies.

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 first sentence names the resource precisely (SKUs and quantities) and the scope (one warehouse), which separates it from the multi-location sibling tools. It stops short of explicitly naming a sibling such as get_item_quantities or get_available_quantities, so the boundary is implied rather than stated.

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 gives a concrete prerequisite — fetch warehouse_id via skuvault_list_warehouses — which is real usage guidance. However, there is no statement of when to prefer this over the several other quantity-reading siblings in the list, so an agent must infer the choice.

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