get_order_status

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

With no annotations, the description carries the load and does the most important job: it corrects the expectation set by the name 'get_order_status', clarifying that only sandbox-local state is returned and live broker status is unavailable. 'Read' also conveys non-mutation. It omits error behavior for unknown or non-local order_ids, which keeps it out of the top band.

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 short sentences with zero redundancy, and the capability statement is front-loaded ahead of the limitation. Every clause carries information an agent needs.

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 return-value explanation is unnecessary, and with one trivial parameter the description covers the main risk: mistaking this for live broker status. Missing are error/empty-result behavior and order_id validity, minor for a single-argument read.

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 description coverage is 0%, so the lone order_id field is undocumented, and the description does not define its format. It does implicitly narrow the meaning to a local sandbox identifier rather than a broker id, which is meaningful but thin compensation for the coverage gap.

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?

'Read one local sandbox order' gives a specific verb (Read), a specific cardinality (one), and a scoped resource (local sandbox order), which cleanly separates it from list_orders. It stops short of naming that sibling outright, so the distinction is inferred 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?

'External broker status lookup is not implemented' is a genuine exclusion that tells the agent this is not a route to live broker state. However, there is no positive guidance on when to pick this over list_orders or how to obtain a valid order_id, so usage is only implied.

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