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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two real facts beyond structured data: results are ordered newest-first, and calls are free. It says nothing about pagination behaviour or what a movement record contains.

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?

Very short and front-loads the ordering, but the telegraphic clause chain with colon and trailing 'Free.' is awkward to parse and omits the subject. Brevity here comes at the cost of clarity rather than from removing waste.

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 7-parameter listing tool with no output schema needs the description to say what a movement record looks like and how pagination behaves; neither is present. Annotations cover safety, but an agent still cannot tell the return shape or default result size from this text.

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 57%; the description maps its 'one item, at one location, of one kind, in a period' phrasing onto sku, location, kind and from/to, which helps confirm those filters are conjunctive. It says nothing about limit/offset pagination or their defaults, and 'Free' is the only comment on cost.

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 fragments convey that this returns stock movements ('Moves') ordered newest first, filtered to one item, one location, one kind and a date period. But 'Moves newest first' reads as a heading rather than a clear verb+resource statement, and nothing distinguishes it from siblings like inventory_report or inventory_list_items.

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?

'Free' implies no cost/credit consumption but there is no guidance on when to use this versus inventory_report, inventory_list_items or inventory_export. No prerequisites, no exclusions, no alternatives are named.

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