list_orders

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

With no annotations, the description must carry the full burden of behavioral disclosure. It conveys that the tool lists orders and supports filtering, but does not mention pagination behavior, default sorting, result limits, or whether it returns full order details or summaries. This is a minimal but non-contradictory disclosure.

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 two short sentences, entirely focused and free of redundant information. Every word earns its place, making it a model of conciseness.

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?

Given the tool has 5 parameters and no output schema or annotations, the description is adequate but leaves gaps. It doesn't clarify return format, pagination mechanics, or behavioral limitations. The schema covers parameters, but the tool's overall behavior and edge cases are under-described.

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 100%, so the baseline is 3. The description's mention of 'status, date' loosely maps to the `query` parameter, but it does not add new meaning beyond the schema's explicit examples and parameter descriptions. No additional semantic value is provided.

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 'Lists orders in the shop' clearly states the verb (list) and resource (orders), immediately distinguishing it from order-specific siblings like get_order, update_order, cancel_order, and create_draft_order. The additional mention of filtering by status/date further narrows the scope.

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?

The description provides clear context ('Lists orders in the shop') and hints at filtering via 'Filterable by status, date, etc.', but it does not explicitly exclude alternatives or state when to prefer this over get_order. It gives enough context for an agent to infer usage but lacks explicit 'when not to use' guidance.

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