orders_ListOrders

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, but it only identifies the underlying SOAP adapter and operation. It says nothing about pagination, filtering behavior, permissions, or what happens with an empty status.

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?

The sentence is short but wastes its space on adapter metadata rather than useful specification. Brevity here reflects under-specification, not efficiency.

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 list operation with an undocumented filter parameter and no output schema, the description omits everything an agent needs: return shape, filtering semantics, and pagination. It is not complete enough to call the tool 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 description coverage is 0% and the single 'status' parameter is undocumented. The description does not describe the parameter's meaning, allowed values, or whether it filters results, leaving the agent with no semantic guidance.

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 description restates the tool name ('ListOrders' on service 'Orders') without adding a specific verb/resource characterization or scope. It gives no indication of what is returned or how it differs from orders_GetOrder, so it functions largely as a tautology of the name.

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 guidance on when to use this tool versus the siblings orders_GetOrder or orders_GetInventory. The only implicit signal is the word 'List' in the name, which is not expanded on.

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