ebay_get_listing

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

No annotations are provided, so the description must compensate. It discloses the API used (Trading API, GetItem), required authentication (OAuth token), and that it returns all listing fields. However, it does not mention side effects, error handling, rate limits, or idempotency, leaving gaps in behavioral coverage.

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, consisting of three sentences that front-load the purpose. No extraneous information is included, and every sentence serves a clear function.

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 retrieval tool with one parameter, the description covers purpose, API, output summary, and auth requirements. It is mostly complete, though it could mention error handling (e.g., invalid item ID). Given the lack of output schema, the description provides sufficient context for the 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?

The input schema provides 100% coverage with a clear description of the 'itemId' parameter. The description only reiterates the parameter's role ('by item ID') without adding meaning beyond the schema, so the baseline 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 resource 'listing', clearly indicating it retrieves full details for a single listing by item ID. It distinguishes itself from siblings like 'ebay_get_listing_set' or 'ebay_get_listing_fees' by focusing on a single listing.

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 implies usage context (single listing by ID) but does not explicitly state when not to use it or provide alternatives. It lacks exclusion criteria and sibling differentiation beyond the name.

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