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

The annotations already declare readOnlyHint=true, and the description corroborates that with 'Read-only'. It adds one genuinely useful behavioral note — orders are pulled live from a saved broker credential and raw credentials must never be passed — but says nothing about latency/live-API cost, pagination, result limits, or what 'recent' means as a time window.

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?

Three short sentences, front-loaded with the read-only/safety constraint, then the narrowing filters, then the security warning. No filler and nothing redundant.

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 7 optional parameters, no output schema, and zero schema descriptions, the description leaves too much unanswered: no default result scope, no order-record shape, no guidance on which credential is used when multiple exist. For a broker-facing read tool this is under-specified.

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 description carries the full burden, yet it only echoes four parameter names (symbol, statuses, startTimeIso, endTimeIso) without format, accepted status values, or timezone/ISO expectations. The remaining three parameters — assetType, brokerProvider, brokerCredentialId — are never mentioned, and the credential warning only indirectly hints at brokerCredentialId.

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 ('fetches ... broker orders') with scope ('current or recent') and source ('directly from a saved broker credential'), which separates it from siblings like get_broker_account_snapshot and get_broker_positions. It stops short of naming those alternatives explicitly, so the differentiation is implicit 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?

'Use symbol, statuses, startTimeIso, and endTimeIso to narrow' gives filtering guidance, but there is no statement of when this tool is preferred over the many adjacent order/telemetry tools (e.g., get_deployment_order_telemetry, get_single_trade_status) or what the default behavior is when no filters are supplied.

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