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 new context the annotations lack — a hard rate limit of 5 requests/minute and the underlying endpoint (POST /purchaseorders/getReceivesHistory). It stops short of explaining auth requirements or how the 'quantity corrections' section is keyed, but the throttle disclosure is exactly the kind of operational detail an agent needs before paginating.

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 dense sentences: purpose and payload first, filters second, operational constraint and endpoint last. No filler, and the most decision-relevant facts are front-loaded.

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?

With no output schema, the description usefully sketches the return content, and pagination semantics live in the schema. What's missing is any guidance on result ordering, expected volume, or whether the corrections section can be excluded — modest gaps for an 8-parameter read tool with a throttled, open-world backend.

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% and includes pagination chaining guidance (`next.page`/`next.skip`), so the schema does the heavy lifting. The description only restates the filter dimensions already documented in the properties, adding no syntax or format detail beyond them — baseline 3.

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 the specific resource (purchase-order receiving history) and even outlines the payload shape — SKU, quantity, location, user, dates plus quantity corrections — which cleanly separates it from skuvault_list_purchase_orders. An agent can tell what this returns without opening the schema.

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 lists the available filters (warehouse codes, PO numbers, received time), which implies when the tool is useful, but it never states when to prefer it over sibling inventory/PO tools or what the trade-offs are. The 5/min throttle hints that bulk/exploratory use is discouraged, but only implicitly.

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