ebay_get_item

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

No annotations provided, so the description must convey behavior. It states 'full details' but does not clarify if the tool is read-only, requires authentication, or has rate limits. The description adds some context (example ID format) but lacks crucial behavioral disclosures.

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?

Single, well-structured sentence with no redundant information. Every word earns its place, providing clear and concise purpose.

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 exists, so the description should compensate by explaining what 'full details' includes. It does not, leaving the agent uncertain about the return structure. Adequate for a simple fetch but incomplete for comprehensive understanding.

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 schema already documents both parameters. The description adds value by providing a concrete example of the item_id format ('v1|123456789|0'), which aids correct invocation. No additional value for marketplace beyond the default mention.

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 the tool fetches full details for a single eBay item by ID, using the verb 'Fetch' and specifying the resource. It distinguishes itself from siblings like ebay_search (which returns multiple items) and ebay_price_check (likely price-focused).

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 (e.g., ebay_search or ebay_price_check). It implies usage when you have a known item ID, but does not provide exclusions or context for sibling tools.

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