ebay_get_orders

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

The description mentions required OAuth scopes, which is useful for authentication context. However, without annotations, it should also disclose pagination, rate limits, or return format, which are missing.

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 short and front-loaded with the main action. It includes necessary OAuth information without unnecessary fluff, making it concise. It could be slightly improved by clarifying scope or result format.

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 absence of annotations and output schema, the description lacks crucial context. It does not state that the tool returns multiple orders (versus 'ebay_get_order'), nor does it explain the return type or pagination behavior.

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?

All three parameters (filter, limit, offset) are described in the input schema with 100% coverage. The description adds no additional meaning beyond what the schema provides, so a baseline score of 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 'Retrieve orders for the seller', which is a specific verb and resource. However, it does not differentiate from the sibling tool 'ebay_get_order', which likely retrieves a single order, leading to ambiguity.

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?

No guidance is provided on when to use this tool versus alternatives like 'ebay_get_order'. There is no information on filtering, pagination, or prerequisites beyond the OAuth scope.

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