hosting_listOrdersV1

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

The description discloses that the tool returns accessible orders, including shared ones, and supports pagination and filtering. With no annotations, it carries the burden, but it omits explicit statement of read-only nature or idempotency. Still informative enough.

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 concise with two paragraphs, front-loading the main purpose and adding details in the second. Slightly verbose with 'Use the available query parameters' but overall efficient.

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 no output schema or annotations, the description covers core functionality and filtering options. It lacks details on response format or pagination defaults, but schema provides parameter details. Adequately complete for a list endpoint.

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?

Input schema descriptions cover all parameters (100% coverage). The tool description references filtering by statuses and order IDs but adds no new meaning beyond the schema. Baseline 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 clearly states the tool retrieves a paginated list of orders for the authenticated client, specifying the resource (orders) and scope (own and shared). It distinguishes from sibling tools like hosting_listWebsitesV1 which deal with different resources.

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 mentions using query parameters for filtering, implying when to use the tool (to get filtered order lists). However, it does not explicitly state when not to use it or provide alternatives, though no direct sibling offers the same functionality.

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