view_order_history

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

With no annotations, the description must disclose behavioral traits. It explicitly notes 'Requires eBay credentials,' which is an important authentication requirement. The verb 'view' implies read-only behavior, but the description does not discuss side effects, output format, or security implications. This is moderate transparency.

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 two concise sentences, front-loaded with the primary purpose. Every word earns its place, with no fluff or repetition.

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?

There is no output schema, so the description should convey what the tool returns. 'Purchase history' implies a list of past orders, but the description does not specify the response structure, the effect of the 'days' parameter, or any error conditions. It is minimally adequate for a familiar concept but lacks completeness for an agent.

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 input schema already describes username, password, and days. The description reinforces the credential requirement but does not add meaning beyond the schema. No additional parameter semantics are provided.

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 a specific verb and resource: 'View your eBay purchase history.' This clearly differentiates it from sibling tools like search_products, get_item_details, track_bids, place_bid, buy_it_now, and track_shipment, which all serve distinct purposes.

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 states the clear context: view your purchase history. It implies when to use it (when you need past orders) but does not explicitly exclude alternatives or mention when not to use it. The credential requirement provides an additional cue, but no direct comparison to sibling tools.

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