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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds content-level context (each adjustment carries reason, status and lines) and cites the underlying endpoint, but says nothing about paging behavior, result volume, or auth requirements beyond what the schema implies.

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 well-formed sentence front-loads the resource, its subtypes, returned fields and filters. The trailing endpoint reference is short and mildly redundant but not disruptive.

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 endpoint with no output schema, the description tells the agent what each record contains and which filters apply, which is close to sufficient. It stops short of describing pagination semantics 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 already documented (including format, ranges and defaults). The description's 'filtered by warehouse, product or date' merely restates three of them and does not explain modifiedSince or the pagination pair. Baseline 3 is appropriate.

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, and the parenthetical '(write-offs, recounts, corrections)' plus 'reason, status and lines' makes clear which record type this covers, implicitly separating it from unleashed_list_stock_on_hand. However, it never names a sibling tool, so the differentiation from the other list_* endpoints must be inferred.

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?

'filtered by warehouse, product or date' implies when the tool is useful, but there is no explicit when-to-use statement, no exclusions, and no pointer to an alternative such as list_stock_on_hand. Usage is only inferable.

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