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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by saying it returns all stock changes and orders them newest first, but it does not discuss pagination behavior or return shape 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?

The description is a single front-loaded sentence that states the resource, ordering, and included movement types without filler. Every part of the sentence contributes to understanding the listing.

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 simple read-only list tool with full schema coverage and rich annotations, the description provides enough context: it identifies the resource, says it is comprehensive, and specifies newest-first ordering. The remaining gap is minor because the schema covers parameters and annotations cover safety.

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 two parameters are already documented in the schema. The description does not add any parameter-specific meaning, such as how item_id filtering interacts with the movement history, so the baseline score of 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?

The description clearly states that the tool returns every change to stock as a newest-first list, and it enumerates the movement types included. It is specific about the resource and ordering, but it does not explicitly distinguish this from sibling tools such as inv_stock or inv_item_stock.

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 description implies a stock-movement history use case through phrases like 'Every change to stock' and 'newest first', but it gives no explicit when-to-use guidance, exclusions, or alternatives. An agent comparing this with inv_stock or inv_item_stock receives no routing help.

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