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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety profile is covered. The description adds that these are orders sent on a session created by fixsim_send_order, which is useful context, but says nothing about pagination behavior beyond what the schema limit param implies, ordering (newest first is in schema), or error/auth conditions.

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, front-loaded with the resource and scope, then the single-fetch option. Nearly zero waste, though 'OUT' capitalization and abbreviation are slightly terse.

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?

For a 5-param list tool with no output schema and low schema coverage, the description covers the core intent and the clOrdId shortcut, but omits auth requirements, pagination, and the distinction from fixsim_list_orders_in. Adequate but with clear gaps.

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 20%: only the limit param is described in the schema. The description adds meaning for clOrdId ('fetch one') and ties instance/session to the sending context, which partially compensates, but apiKey and the full semantics of session/instance remain undocumented.

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?

Clear verb+resource: lists orders FIXSIM sent outbound on a session. Names a related tool (fixsim_send_order) as the creator of these orders, and distinguishes 'out' from 'in' implicitly. However it doesn't explicitly contrast with fixsim_list_orders_in, so sibling differentiation is partial.

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?

Implied usage: list outbound orders, or pass clOrdId to fetch a single one. There is no explicit when-to-use vs fixsim_list_orders_in or other alternatives, and no stated prerequisites (e.g., auth/session requirements).

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