list_orders

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

readOnlyHint=true already establishes this is a safe read, so the description's only added context is the "so far" time scope and the optional mission narrowing. It says nothing about pagination, result ordering, volume limits, or what happens when mission_id is invalid — meaningful gaps for a list operation even against a lower annotation bar.

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?

One compact sentence with the filter qualifier at the end; nothing is wasted. The phrasing "ordered so far" is slightly ambiguous about time boundaries, which keeps it out of the top band.

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?

This is a list tool with no output schema and no annotations describing returns, so the description is the only place return shape, ordering, and pagination could be explained — and none of it appears. For a listing endpoint that gap matters more than it would for a single-object getter.

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 must carry mission_id, and it does partially: it clarifies the parameter is optional and scopes results to a single mission. It adds no format or ID syntax, so it is a partial compensation rather than a full one.

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?

"Orders placed so far, optionally for one mission" largely restates the name list_orders, adding only the temporal scope and the optional mission filter. It gives no differentiation from siblings like get_order (single order) or search_catalog/place_order, so an agent must open the schema to know whether this is a bulk listing or a filtered search.

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?

There is no explicit when-to-use statement, no mention of the alternative get_order for retrieving one order, and no guidance on when to pass mission_id versus omitting it. The optional filter is mentioned but the conditions that select it are left to inference.

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