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

Goes well beyond the readOnly/idempotent/destructive annotations: it discloses that stocks use real Alpaca paper status while perps/predictions use virtual receipts, that 'accepted/working is not filled', that reads never create or fund accounts, that broker failure surfaces explicitly, and that an agent key is required. This is unusually rich behavioral context for a read 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?

Front-loads the core action in the first clause, then packs several short informative sentences with minimal waste. Slightly dense jargon ('lane/source', 'UD5M', 'virtual receipts') slightly reduces immediate clarity but each sentence 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?

With no output schema, the description usefully explains status interpretation ('accepted/working is not filled') and data-source differences, which is the key return-value context an agent needs. It is nearly complete for a read tool whose safety profile is already covered by annotations.

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 only 50% (order_id has no description). The phrase 'explicit lane/source' gestures at routing but is jargon that never maps cleanly to the `competition` parameter, which the schema itself documents as the competition sub-book scope. The description adds little meaning beyond the partial 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?

States a specific verb and resource ('Read YOUR order by ID') and adds scoping detail ('explicit lane/source'), which lets an agent distinguish this single-order read from get_my_orders. It does not name a sibling explicitly, so differentiation is implied rather than stated.

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 'by ID' framing implies when to use it versus list-style reads, and 'Reads do not create or fund accounts' gives a scope boundary. However, there is no explicit when/when-not statement and no named alternative (get_my_orders, get_order_timeline), leaving routing to inference.

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