ebay_get_ads_by_listing_id

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

With no annotations provided, the description ('Returns all ads') correctly indicates a read-only, non-destructive operation. However, it lacks details on potential behavioral traits such as rate limits, response size, or whether it requires specific permissions, leaving some gaps for an agent.

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 two short sentences that convey the purpose and basic behavior without unnecessary details. Every word adds value, making it easy for an agent to quickly understand.

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?

Given the absence of an output schema, the description does not mention the return format, pagination, or any limits on the number of ads returned. This incomplete information could lead to assumptions about the response structure, which is a notable gap for a retrieval tool.

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 has 100% coverage with clear descriptions for 'listingId' and 'campaignId'. The tool description adds no additional meaning beyond the schema, so it meets the baseline expectation but does not enhance parameter understanding.

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 action ('Get ads') and the resource ('by listing ID'), with a concise explanation that it returns all ads for a given listing. This distinguishes it from sibling tools like ebay_get_ads (which retrieves all ads) and ebay_get_ads_by_inventory_reference (which uses a different reference).

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 explicitly states when to use the tool: to retrieve ads for a specific listing identified by listing ID. It implies context by contrasting with siblings, but does not explicitly provide exclusions or alternative tools for different scenarios (e.g., retrieving all ads).

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