list_orders

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description adds no additional behavioral context. It only restates the read-only nature ('fetch') and provides no details about pagination behavior, result ordering, or any other runtime characteristics beyond what annotations already convey.

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 description is a single, concise sentence 'Fetch a list of orders' with no unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent to quickly parse.

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?

The tool is relatively simple with an empty required-parameter set and a clear schema. However, the description lacks any mention of when to use 'list' over 'search' (given the sibling 'search_orders'), and it does not explain the scope of the listing (e.g., all orders vs. filtered). This leaves a notable gap in context for tool selection.

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?

All three parameters (limit, offset, order_by) have descriptions in the schema, providing 100% coverage. The description itself does not add any parameter semantics, but the schema already fully documents the parameters, so the baseline of 3 is appropriate.

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 'Fetch a list of orders' clearly states the action (fetch) and resource (orders), making it a specific verb+resource combination. However, it does not differentiate from the sibling tool 'search_orders', which likely serves a similar purpose with more filtering capabilities.

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 alternatives like 'search_orders'. The description does not mention pagination, recommended use cases, or any exclusions. This leaves the agent without context for selecting the correct tool among many list/search siblings.

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