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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds useful context beyond that: pagination behavior, the location-scoping constraint, and the 'Admin API' label implying admin-level auth. It still says nothing about default page size behavior beyond what the schema states or about ordering/return shape.

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 clauses, front-loaded with the core action and followed by the terminology clarification, the filtering hint, and the endpoint. Nothing is padded, though the endpoint reference is marginal for an agent that already has tool routing.

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 three-optional-parameter read-only list tool with full schema coverage and no output schema, the description covers purpose, paging, and filtering adequately. It leaves return-item shape undescribed, which is a minor gap given there is no output schema.

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%, with each parameter (page, size, location_ids) fully documented including defaults and max. The description's 'with paging' and 'narrow by location ids' merely echo that, adding no syntax or format detail, so 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 description states a specific verb and resource ('List stock items') and disambiguates the domain term by noting these are the physical units the API calls 'articles', plus the underlying endpoint. It does not explicitly contrast itself with nearby siblings such as get_stock_item or list_skus, 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?

It says to 'narrow by location ids', which implies the supported filtering scenario, but gives no when-to-use versus alternatives (e.g., prefer get_stock_item for a single unit, or list_skus for SKU-level data). Usage is implied rather than prescribed.

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