get_order

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

No annotations exist; description discloses required API credentials, return fields, and that market_id is optional despite the spec. This is sufficient transparency for a read-only lookup tool.

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?

Three sentences cover purpose, parameter nuance, and authentication requirement with no wasted words. Critical information is front-loaded.

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 two-parameter tool with no output schema, the description includes return fields, parameter behavior nuance, and authentication requirement, making it fully actionable.

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 already documents both parameters with 100% coverage. The description adds nuance about market_id's routing purpose and current gateway behavior, providing context beyond 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 ('Get') and resource ('a single order'), specifies what fields are returned (status, fills, remaining size), and distinguishes from sibling tools like get_open_orders and get_order_history which handle multiple 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?

Provides guidance on when to include market_id and notes the gateway behavior. Does not explicitly list alternative tools for different contexts, but the sibling tool list itself helps agents select appropriately.

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