get_orders

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

No annotations are provided, so the description carries the full burden. It describes the tool as a read operation but does not disclose pagination, ordering, limits, or the default time range for 'recent'. The explanation of returned fields is helpful but incomplete.

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 description is a single, well-structured sentence that front-loads the core purpose. It is concise and includes key result fields, but lacks some structure (e.g., bullet points) for clarity.

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 simple read operation with no output schema, the description adequately lists the returned fields (status, marketplace, totals, items, shipping details). It is sufficient for basic use, though details on pagination or sorting are 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% (start_date, end_date), so the baseline is 3. The description adds 'recent' but does not clarify parameter behavior (e.g., what happens if both are omitted). No extra semantic value over the schema.

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?

The description clearly states the verb 'Read' and the resource 'Amazon orders', listing the specific fields included (status, marketplace, totals, items, shipping details). This distinguishes it from sibling tools like get_product_details or get_fba_inventory.

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 use for retrieving order details but provides no explicit guidance on when to prefer this tool over alternatives (e.g., get_campaign_performance, get_settlement_economics). No exclusions or context for date range handling.

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