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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered structurally. The description adds that results are per-item/per-facility totals split into on-hand, allocated and available buckets, which is genuinely useful context, but says nothing about volume, pagination behavior, or account/facility scoping.

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?

Two short sentences, front-loaded with what the payload contains before the filtering hint. The trailing 'GET /inventory/stocksummaries' is largely redundant for an agent but is cheap, so the description is efficient without being optimal.

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?

With no output schema, the description does roughly what it needs to by naming the three quantity fields returned. Pagination is fully handled by the schema (pgnum/pgsiz with guidance), so the only real omission is how this differs from the closely named sibling list_stock_details.

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% and each parameter is well documented in the schema, so the baseline is 3. The description adds a concrete filter example (`ItemId==123`) that differs slightly from the schema's `ReadOnly.CustomerIdentifier.id` example, offering a small amount of extra signal but no syntax or semantics 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?

States a specific resource and what it contains ('Inventory totals per item and facility (on hand, allocated, available)'), which is more informative than the title alone. It does not distinguish itself from the close sibling extensiv_list_stock_details or extensiv_list_inventory, so it falls short of a 5.

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?

'Filter with rql, for example `ItemId==123` or a customer filter' gives a hint on how to narrow results, but there is no statement of when to reach for this tool versus extensiv_list_stock_details or extensiv_list_inventory, nor any exclusions or prerequisites. Usage is implied rather than guided.

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