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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-derivable behavior: a hard 7-day maximum range and heavy throttling at 5 requests/minute, both of which change call pacing. Output shape is only partly described, so not a 5.

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?

Three front-loaded sentences: what it returns, the hard constraint, then filters, throttle and endpoint. Dense and waste-free, though the filter enumeration and the trailing endpoint path carry little value for an agent that already has the schema.

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 12-parameter read tool with no output schema, the description covers return fields, the range cap, filter dimensions and rate limits. What's missing is pagination behavior explanation and any note that results are paginated windows, though the schema covers both adequately.

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%, with the 7-day rule, page/skip chaining, limit windowing and warehouse id sourcing all already in the schema. The description's filter list restates the same fields without adding format or semantics, so 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?

Names a specific resource (inventory transaction history) and enumerates what each record contains (user, SKU, quantity before/after, location, reason, note, sale). This clearly distinguishes it from the sibling quantity/stock tools, which report current state rather than movement history.

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 framing as a history/audit tool implies when to reach for it, and the 7-day window plus filter list implies it's a scoped query rather than a bulk export. But no sibling is named and there is no explicit 'use this instead of X when...' guidance, leaving the agent to infer the split from tool names.

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