List orders

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description consistently describes a read operation. It adds useful context about data scope ('hosting accounts' and 'shared access') and pagination, but does not disclose response shape, pagination defaults, or rate limits. This meets the baseline but is not rich.

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?

Three sentences, front-loaded with the core action, followed by scope and filter guidance. It is compact and readable, though the final sentence largely restates schema information that is already explicit in the input schema.

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 read-only list operation with fully documented optional parameters, the description covers the essential selection context: hosting orders, shared access, pagination, and filtering. It does not describe the response structure, and no output schema is available, but this is a minor gap for correct invocation.

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 page, per_page, statuses, and order_ids are already fully documented. The description only advises using these filters and adds no new meaning beyond what the schema provides.

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 opens with a specific verb and resource: 'Retrieve a paginated list of orders.' It further distinguishes itself by scoping the result to the authenticated client's hosting accounts plus orders from shared access, which separates it from sibling order-list tools such as ecommerce_listStoreOrdersV1 and mail_listOrdersV1.

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 for when to use the tool: when listing hosting-account orders, including those shared with the client. It does not explicitly name alternative tools or state 'do not use when...', so it stops short of full routing guidance.

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