amazon_get_order

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the access scope ("one of the person's own" orders, implying no cross-account access) and what categories of data are returned, but says nothing about behavior for an unknown/foreign order id, auth requirements, or idempotency of the call — and the truncation removes whatever followed.

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?

The single-sentence shape is efficient and front-loads the resource, but the text is truncated mid-word, leaving an incomplete thought. The (Beta) marker is low-value relative to the missing usage guidance.

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?

No output schema exists, so the field enumeration (items, totals, shipments, payment kind) does real work here. Still missing: how the order is addressed given an empty input schema, and what happens on failure — both material gaps for a lookup tool.

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?

The schema declares zero properties, yet the description states the order is identified "by its id" — a parameter that does not exist in the input schema. That mismatch is worse than silence, because an agent cannot tell whether an id argument is accepted, required, or must be embedded some other way.

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 ("Shows") and resource ("one of the person's own Amazon orders") and enumerates the returned fields (items, totals, shipments, payment kind), which distinguishes a single-order fetch from list/search siblings. The sentence is cut off mid-word ("and sh..."), so the purpose statement is not fully delivered.

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 "by its id" phrasing implies a single-record lookup, but there is no explicit guidance on when to use this instead of amazon_list_orders or amazon_search_orders, nor any stated prerequisite (e.g., how an order id is obtained). No when-not-to-use condition is present.

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