public_list_orders

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: no pagination behavior, no default ordering, no note on whether results are scoped to the caller's public account.

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 words are technically concise and front-loaded, but here brevity reflects under-specification rather than economy of language. The description is too small to earn its place as documentation for a five-parameter filtered list tool.

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 five-parameter listing endpoint with pagination and date-range filters and no output schema, the description says nothing about filtering, paging, date formats, or the public-scope semantics implied by the name. Only the annotations cover part of the picture, leaving the description materially incomplete.

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% with five documented parameters (offset, status, start_date, end_date, page_size), so the schema carries the full semantic load. Per the high-coverage baseline, a 3 is appropriate even though the description contributes no parameter information at all.

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?

"List Orders" essentially restates the tool name public_list_orders and the annotation title "Public List Orders" without adding scope, filters, or the public/order-domain framing. It is a verb+resource, but nothing distinguishes it from siblings like public_get_order, public_get_order_deliverables, or list_assets.

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 when-to-use guidance, no mention of the public-facing nature of the endpoint, and no pointer to alternatives such as public_get_order for a single order. Nothing is said about when this tool is appropriate versus the other order endpoints.

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