get_draft_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 discloses the response contents ('Returns full draft order including line_items, customer, address, and applied discounts') but does not explicitly confirm read-only behavior, error handling, or permissions. 'Get' implies non-mutating, but more transparency would be beneficial.

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 sentence that states the purpose and key return information. It is concise, front-loaded, and every word earns its place.

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 getter with 1 parameter and no output schema, the description covers the essential return contents ('line_items, customer, address, and applied discounts'). It does not mention error behavior or explicitly state read-only, but overall it is sufficient for a tool of this complexity.

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%: the only parameter, draft_order_id, is already described as 'Draft order ID (numeric). Required.' The description adds no extra semantic meaning beyond what the schema provides, so baseline 3 applies.

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 'Get a single draft order by ID' uses a specific verb and resource, clearly distinguishing it from siblings like list_draft_orders (plural) and get_order (regular orders). It states exactly what it does.

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 usage (when you have a specific draft order ID), but it does not explicitly mention alternatives or when-not-to-use. There is no comparison to list_draft_orders or get_order, so guidance is only implied.

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