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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuine behavioral fact not in the structured data — results come back newest first — but says nothing about default page size or the legacy bare-array response shape beyond what the schema already documents.

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 with zero filler and the ordering trait folded into the same clause. It is efficient, though the extreme brevity leaves the overall definition thin rather than rich.

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?

A simple read-only list tool with a fully documented schema and complete safety annotations doesn't need much, and the ordering note is useful. Still, an agent gets no signal about the stock_item_search alternative or the default page size, which are the main decisions this tool requires.

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 property descriptions already explain limit bounds, cursor opacity, and the legacy bare-array-versus-{items,next_cursor} behavior in detail. The description adds no parameter meaning on top of 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 and resource ('List your stock_item rows') that is distinct from the write/read siblings like stock_item_create and stock_item_read. However, it never distinguishes listing from stock_item_search, and 'your' only loosely conveys the tenancy scope.

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 choose this over stock_item_search or how it relates to stock_item_read. The only usage hint is the parenthetical ordering, which does not tell an agent which tool to pick.

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