get_order

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 return format (JSON) and accepted ID formats (GID or numeric ID with auto-promotion). It doesn't mention error cases or authentication, but for a simple fetch operation, it is adequately transparent.

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?

Two sentences with no wasted words. The first sentence clearly states the tool's purpose and what it returns. The second provides usage guidance. Structure is front-loaded and efficient.

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 tool with one required parameter and no output schema, the description covers everything needed: what fields are returned, ID format, and how to discover IDs. It also connects to related tools (list_orders, list_fulfillment_orders).

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 single parameter 'id' has a schema description that is 100% complete. The description adds extra context about accepting both GID and numeric ID forms, that numeric IDs are auto-promoted, and where to get an ID (list_orders).

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 'Fetch a single order's full record' and lists specific fields (email, totals, status flags, timestamps, line items, customer email). It distinguishes itself from sibling tools like list_orders and list_fulfillment_orders.

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 advises to 'Use list_orders to discover order IDs first' and suggests a follow-up with list_fulfillment_orders for shipments. This provides clear when-to-use and which alternative tools to use.

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