order_status

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

No annotations, but description conveys read-only intent (status lookup) and highlights eventual-consistency of alternative. Could explicitly state it does not modify state, but context is sufficient.

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?

Two concise sentences: first defines purpose and outputs, second provides usage context. Zero fluff, highly efficient.

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?

Complete for a simple lookup tool: explains purpose, output fields, and when to use. Without output schema, it covers essential context. Could mention read-only explicitly.

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 has 0% coverage for parameter description; tool description adds meaning by identifying `order_id` as identifier of a placed order. Single parameter is well-contextualized.

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?

Clearly states it provides status of a placed order by order_id, listing return fields (state, filled quantity, average price). Distinguishes from siblings via explicit contrast with `positions`.

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 directs to use after buy/sell to confirm fill, and warns that `positions` lags. This provides clear when-to-use and when-not-to-use guidance.

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