ebay_get_orders

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states that the tool retrieves orders and requires specific scopes, but fails to mention if the operation is idempotent, safe, or has rate limits. This is insufficient for a mutation-aware agent.

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 very concise (1 sentence plus scope lines) and front-loads the core purpose. It could include slightly more detail without becoming verbose, but the brevity is generally effective.

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 complexity (5 parameters, no output schema, many siblings), the description is incomplete. It does not explain pagination, filtering behavior, return value structure, or how it differs from 'ebay_get_order'. An agent would need to infer too much.

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?

The input schema has 100% description coverage for all 5 parameters, so the schema already documents each parameter. The description adds no additional meaning beyond what is in the schema, hence a baseline score of 3.

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 that the tool retrieves orders for the seller, which is a specific verb and resource. However, it does not differentiate from the sibling tool 'ebay_get_order' (singular), leaving ambiguity about when to use each.

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 OAuth scope requirements, which is important context for using the tool. However, it does not specify when not to use this tool, nor does it mention alternatives like 'ebay_get_order' for single order retrieval.

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