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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered without the description. The description adds value by naming the required OAuth scope ('items.read'), which annotations do not convey. It omits detail on pagination semantics, but the schema carries that fully.

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?

One sentence, front-loaded with the verb and resource, followed by the scope requirement. Every clause carries information; nothing is padding.

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 zero-required-param, read-only list tool with a fully documented schema and rich annotations, the description covers purpose, subject matter and the auth scope. The only remaining gap is routing guidance versus the search/get siblings, which is a selection issue rather than a missing invocation detail.

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 the paging cursor, embed, field and limit parameters are documented in detail in the schema itself. The description's only contribution is 'with paging', which adds no syntax or behavior beyond what the schema states, 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 (catalog items), and goes further by enumerating the item subtypes (products, services, shipping, packaging), which an agent cannot infer from the name alone. It does not distinguish itself from the sibling sellsy_search_items or sellsy_get_item, 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?

The prerequisite 'Needs items.read' is a useful gating condition for invocation, and the description implies bulk retrieval. However, there is no explicit guidance on when to pick this over sellsy_search_items (filtered lookup) or sellsy_get_item (single record), leaving the agent to infer the choice.

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