get_order

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

With no annotations provided, the description carries the full burden and does well by stating that the tool is read-only, exposes no secrets, performs no order-flow control, and never exposes the opaque pre-trade lock. It does not mention error behavior for missing ids, permissions, or rate limits, but its safety and exposure disclosures are substantial.

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 front-loaded and appropriately short for a simple retrieval tool. The final sentence slightly restates the display-price and hidden-lock point, but the content remains tightly focused.

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?

An output schema exists, so the description need not explain return values in full. For a one-parameter read tool, it covers the key behavioral constraints and hidden-data guarantees, though it could mention missing-order behavior or access requirements.

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?

There is one parameter and schema description coverage is 100%; the schema already says the id is 'Order id returned by submit_order.' The description adds only that the order is 'addressed by its id,' without extra format, validation, or sourcing detail 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 states a specific action and resource: return one order by id, and it enumerates the returned parts (status, approval, fills with display prices). This clearly separates it from list-style siblings like list_orders, but it does not explicitly distinguish itself from check_order.

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?

Usage is only implied by the phrase 'addressed by its id.' The description does not say when an agent should choose get_order over list_orders or check_order, nor does it state any exclusions or prerequisites.

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