hosting_listOrdersV1

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

The description discloses that the endpoint is read-only (retrieve) and paginated, and mentions the scope of access. With no annotations, this covers key behavioral aspects, though could explicitly state it's safe/read-only.

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 concise sentences with the main action first, followed by scope and filtering hints. No wasted words.

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 list tool with 4 parameters and no output schema, the description provides sufficient context about functionality and filtering. It could mention pagination details but is adequate.

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 coverage is 100%, so the parameter descriptions in the schema are sufficient. The description adds no extra meaning beyond hinting that filters are for targeted results, so 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 verb 'Retrieve', resource 'orders', and scope 'accessible to the authenticated client'. It distinguishes from sibling tools by specifying that it includes both own and shared hosting orders.

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 explains when to use the tool (for listing orders, including shared ones) and mentions using query parameters for filtering. However, it does not explicitly state when not to use or provide alternative tools.

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