get_order_history

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

Adds behavioral details beyond annotations: defaults (50/90 days), maxes (100/365), field list, and pagination behavior ('if page_full, re-query higher/wider'). Annotations already declare readOnlyHint=true and destructiveHint=false, so no contradiction.

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?

Single sentence conveys defaults, fields, use cases, and pagination advice without waste. Front-loaded with key constraints (defaults and maxes). Efficient and well-organized.

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 returned fields and pagination, essential for a read-only tool with no output schema. Lacks mention of ordering (likely most recent first) and error handling, but given low complexity and presence of openWorldHint, it is nearly complete.

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 coverage is 100%, so baseline 3 applies. Description repeats default and max values already in schema descriptions for max and days. Adds no new meaning for intent parameter beyond what schema says ('one short line stating who this is for'). No marginal value added.

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?

Description clearly specifies verb+resource: 'Past orders' with returned fields (store, items, total, order_uuid, is_reorderable, fulfillment_type). Differentiates from sibling tools like get_order_status or get_receipt by focusing on historical data.

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?

Explicitly states when to use: analyze habits, find reorder targets, locate a past order. Includes pagination hint. However, does not explicitly exclude alternatives like get_order_status or reorder, leaving some inference up to the agent.

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