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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context by naming the fields returned and the underlying endpoint, but says nothing about pagination behavior or result size limits beyond the schema.

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 tight sentences: the primary scope and returned fields come first, followed by the filtering capability and endpoint. Every element earns its place with no redundancy.

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?

There is no output schema, but the description compensates by enumerating the returned fields (item ids, descriptions, units), and pagination is fully covered by the schema. An agent has enough to call it correctly, though a note on the parent-child relationship to other listing tools would complete it.

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% and all five parameters are documented in the schema, so the schema carries the semantics. The description's rql example (`sku==ABC-1`) adds a concrete filter hint but is a different example than the schema's, providing marginal extra value rather than new meaning.

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 and resource ('List the items (SKUs) of one customer') and names the returned fields (item ids, descriptions, units). It doesn't explicitly distinguish itself from the similar sibling extensiv_list_receiver_items, so it stops short of full differentiation.

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?

Implies usage through the rql filter example and the required customer_id context, giving an agent a sense of when this tool applies. However, there is no explicit when-to-use versus alternatives guidance or exclusion criteria relative to sibling listing tools.

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