ebay_get_conversations

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

No annotations are provided, so the description must carry the full burden. It discloses pagination but omits critical behavioral traits such as authorization requirements, read-only nature, rate limits, or what happens with large result sets. The description is insufficient for an agent to understand side effects or constraints.

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?

A single, well-structured sentence that front-loads the key information (action, resource, pagination). No unnecessary words.

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 tool is a simple paginated list retrieval without output schema, the description is adequate but minimal. It does not explain what data is returned (e.g., conversation IDs, messages, participants) or how filtering works. Sibling tools exist that might require fuller context.

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% with descriptions for 'filter', 'limit', and 'offset'. The description adds 'paginated' hinting at limit/offset usage but adds no new meaning beyond the schema. Baseline score 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 clearly states the tool retrieves all buyer-seller conversations and indicates pagination. It distinguishes from sibling 'ebay_get_conversation' which suggests a single conversation retrieval.

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 use for fetching all conversations with pagination but provides no explicit guidance on when to use this versus alternatives like 'ebay_get_conversation' or filtering conditions. No when-not-to-use or context for siblings.

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