get_order

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

With no annotations, the description carries the full behavioral burden and does disclose the auth requirement ('Requires API credentials') and a genuine runtime nuance — the spec marks `market_id` required for routing while the gateway currently resolves without it. It does not cover error or failure behavior, but the disclosed quirks are exactly the kind of value structured fields cannot provide.

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 deprecation warning is front-loaded, and every subsequent clause (returned fields, market_id nuance, auth) adds distinct information. No filler sentences.

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 two-parameter single-entity lookup with no output schema, the description covers identity, returned fields, the ambiguous parameter, auth needs, and migration path. Nothing an agent needs to call it correctly is 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 coverage is 100% (baseline 3), but the description adds meaning the schema does not: the schema frames `market_id` as merely 'Optional but recommended' whereas the description explains the spec-required-vs-gateway-actual discrepancy, which materially changes how an agent should treat the parameter.

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?

States a specific verb and resource ('Get a single order by its id') and immediately differentiates itself from the nearly-identical sibling `fetch_order` by declaring itself deprecated. An agent can tell exactly what it returns (status, fills, remaining size) without opening the schema.

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 routes the agent away from this tool to `fetch_order`, and gives a conditional rule for `market_id` ('Pass when known'). Both the when-to-use and the primary alternative are named, leaving no inference required.

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