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

readOnlyHint=true already establishes the safe read profile, and the schema already documents that location_code 'adds goods on hand quantity and cost.' The description restates that effect and adds the returned field set (price, unit, VAT, accounts), which is useful but largely duplicates structured data. No pagination, permission, or rate-limit context is added.

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 compact sentences with the scope front-loaded and no filler; the filter list and the location_code behavior follow logically. The trailing 'POST /api/v1/getitems' is minor metadata but costs almost 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?

With six optional params, no output schema, and full schema coverage, the description supplies the missing return-shape context (price, unit, VAT, accounts) and the conditional stock/cost behavior. An agent has enough to call it correctly, though guidance on result pagination beyond max_results is absent.

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%, so the schema already defines every parameter, including the partial-match semantics of code/description and the type enum values. The description's filter list adds no syntax or format detail beyond that, 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?

States a specific verb (List) and resource (items, services and stock articles) plus the returned attributes (price, unit, VAT, accounts), which is well beyond a tautology. It does not differentiate itself from the many other merit_list_* siblings, so it stops 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 enumerates the available filters ('code or description (partial), type, id') and notes what location_code does, implying how to narrow results. However, it never says when this tool is the right choice versus the other list/report siblings, and there are no explicit exclusions.

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