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

readOnlyHint=true already tells the agent this is a safe read. Beyond that, the description discloses the shape of the returned records (reason, status, lines) and the underlying REST route GET /StockAdjustments/{page}, which is genuinely useful given no output schema exists. It stops short of describing pagination semantics or rate limits.

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 sentences, no filler. The purpose and record contents are front-loaded, and the endpoint reference is a compact trailing detail.

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 read-only list tool with full schema coverage and no output schema, the description supplies the missing return-content context and identifies the filter dimensions. Only minor gaps remain, such as any hint about default page size behavior or result ordering.

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 all six parameters are documented in the schema itself, including patterns, ranges and defaults. The description only echoes the filterable dimensions (warehouse, product, date) without adding syntax or format detail beyond the schema — the baseline 3 for fully-covered schemas.

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 (List) and resource (stock adjustments), then defines what qualifies with concrete examples — write-offs, recounts, corrections — and the filterable dimensions. This clearly separates it from the close sibling unleashed_list_stock_on_hand, which reports holdings rather than adjustment transactions.

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 when the tool is useful by naming the filter axes (warehouse, product, date), but it never states when to prefer this over list_stock_on_hand or any other sibling, nor any prerequisites. Usage is inferable but not guided.

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