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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), yet the description adds materially more: it verifies the action belongs to the signed-in user, performs a fresh same-account broker-order observation, and returns Lambda request ids, timings and sanitized errors. It also flags the interpretive caveat that 'a submission receipt alone cannot establish current fill state' and names brokerOrderRead and singleTradeResultSource as the fields to check.

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-loaded and information-dense with no filler, but it contains a garbled duplicated fragment ('broker_orders(action="manage") or broker_orders(action=manage)') and the latter half is a long run-on covering auth, returns, and interpretation in one block. Tightening those would cost nothing in content.

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?

There is no output schema, so the description must convey return values — it does, naming the approval/execution state, the fresh broker-order observation, request id, timings, sanitized errors, and the two fields to interpret. For a read-only status tool with three optional params, an agent has everything needed to call and read it correctly.

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 0%, so the description carries the burden, and it does most of it: actionId provenance is given, and singleTradeBotId/managerBotId are described as the deterministic 'single-trade-<actionId>' form. It stops short of stating whether the parameters are mutually exclusive alternatives or which one wins when several are supplied, which is a real gap for a 0-required-param tool.

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 opening sentence gives a specific verb plus resource and scope: 'Read-only approval and execution status for a direct trade or an existing-order cancel/modify request.' It also draws an explicit boundary against the telemetry siblings ('A broker order id or approval actionId is not a deploymentId; deployment telemetry describes deployed bots instead'), so an agent can separate it from get_deployment_action_status without opening either 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?

It states source and trigger conditions concretely: pass the actionId returned by place_trade or broker_orders(action=manage), and use this tool 'even when no strategy or bot deployment exists.' The exclusion is equally explicit — deployment telemetry is for deployed bots — which is the main confusion risk for this family of status tools.

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