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 value by disclosing the underlying endpoint and the shape of returned records (number, name, price, stock, accounts), but says nothing about pagination behavior, defaults, or result volume beyond what the schema states.

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 compact clauses with zero padding; the resource and returned fields are front-loaded before the endpoint reference. Efficient, though the bare endpoint string is of marginal value to an agent that cannot call HTTP paths directly.

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 read-only list tool with a fully documented 9-parameter schema, the description is adequate but thin — it omits pagination semantics (next_start), default row counts, and sorting defaults, all of which live only in the schema. Nothing critical is missing, but it does not round out the 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 description coverage is 100%, so all nine parameters (sort, dir, limit, query, start, filter, category_id, only_active, only_restock) are already fully documented in the schema. The description adds no parameter meaning 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 resource (inventory articles, clarifying they are products and services) and enumerates the returned attributes (number, name, price, stock, accounts), so an agent knows exactly what it retrieves. It does not explicitly contrast itself with the sibling cashctrl_get_article, but the 'list' framing makes the distinction reasonably inferable.

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?

There is no guidance on when to use this tool versus cashctrl_get_article for a single article, nor any stated prerequisites or when-not conditions. The agent must infer usage entirely from the name and endpoint.

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