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

Annotations only declare readOnlyHint/openWorldHint/destructiveHint, so the description carries real behavioral information beyond them: null vs synthetic-zero pricing, item_price_source='amazon_order_tracking_report' enrichment, pending values being non-final, and what each pallet_delivery_requirement value does and does not mean. This is unusually rich disclosure for a read tool.

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?

Front-loaded with the grain and prerequisites, and most sentences carry distinct semantic load (null handling, pallet semantics, pending caveats). It is dense and long, with the pallet_delivery_requirement explanation bordering on more than the selection task needs, but nothing is truly wasted.

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?

Covers prerequisite, scope, grain, data-quality caveats, and sibling routing; an output schema and read-only annotations are present, so return-shape and safety details need not be repeated. Nothing required to call this correctly is missing.

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 the schema already documents all four parameters; the description's purchase_date note ('seller reporting date') largely restates it. The added detail is mostly about output fields rather than parameter semantics, so the 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 ('inspect one order's header and line items') plus an explicit grain ('single order with item-level ASIN/SKU/title/quantity/price'), which cleanly separates it from get_orders and get_order_items. An agent can route to it 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?

Gives a prerequisite ('Use after you know an Amazon order_id') and explicit exclusions with named alternatives ('Do not use for order discovery or sales totals; use get_orders or get_sales_summary first'). That is when-to-use, when-not, and alternative routing in one place.

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