ebay_get_order

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

No annotations provided. Description only states it retrieves order details and lists OAuth scope. Does not disclose rate limits, response format, or side effects. For a read operation, the description fails to add behavioral context beyond the bare minimum.

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?

Very concise: one sentence for purpose plus scope. Front-loaded with action and resource. Efficient use of space, though could include a brief note on return format without being verbose.

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?

No output schema, so description should explain what is returned. It does not. For a simple tool this is adequate but lacking completeness. Considering the complexity and richness of sibling tools, more context would help.

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 baseline is 3. Description adds OAuth scope but does not elaborate on parameter usage or formats beyond what the schema provides. No additional semantic value.

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?

Name and description clearly indicate the tool retrieves details of a specific order. The verb 'Get' and resource 'order' are specific and unambiguous. Distinguishes from sibling ebay_get_orders (plural) which lists 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?

No guidance on when to use this tool versus alternatives. For instance, there is no mention of when to prefer ebay_get_order over ebay_get_orders or other order-related tools. No exclusions or context provided.

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