ebay_get_order

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions OAuth scope but does not clarify whether the operation is read-only, destructive, has side effects, or what the response structure is. This is insufficient for a tool with no annotation support.

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 extremely concise at two sentences plus the scope line. Every part earns its place, providing the tool purpose and requirement without any fluff.

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 simple tool with one parameter and no output schema, the description adequately states the purpose and authentication requirement. However, it lacks details on the expected response format or any common fields, leaving the agent somewhat in the dark about what information will be retrieved.

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 schema has 100% coverage with a single parameter (orderId) described as 'The unique order ID'. The description does not add any additional meaning or format details beyond the schema, so the 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 uses the specific verb 'Get' and the resource 'a specific order', clearly indicating the action and resource. It distinguishes from sibling tools like ebay_get_orders, which retrieves multiple orders, and ebay_get_order efficiently targets a single order.

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 includes the required OAuth scope, which is helpful for authentication. However, it does not provide explicit guidance on when to use this tool versus alternatives like ebay_get_orders, nor does it specify prerequisites or contexts where this tool should be preferred.

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