ebay_get_conversations

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It mentions 'paginated' but does not explain pagination behavior (e.g., default limit, offset handling), ordering, or whether the response includes metadata like total count. This is insufficient for a tool with 9 parameters and no output schema.

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 at one sentence, front-loading the core purpose and pagination hint. Every word is necessary, and there is no wasted text. It is well-structured for quick parsing.

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 has 9 parameters, no output schema, and no annotations, the description is too sparse. It does not explain the return format, how to handle pagination (beyond mentioning it), or the relationship to other tools like 'ebay_get_conversation'. More context is needed for an agent to use this correctly.

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 each parameter described clearly. The description adds no additional semantic value beyond the schema, but given high schema coverage, a baseline score of 3 is appropriate. No further clarification on parameter usage beyond schema definitions.

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' and the resource 'all buyer-seller conversations', which is specific and actionable. However, it does not differentiate from the sibling tool 'ebay_get_conversation' (singular), which likely retrieves a single conversation, leaving ambiguity about when to use each.

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 usage guidelines are provided. The description does not specify when to use this tool over siblings like 'ebay_get_conversation' or 'ebay_search_messages', nor does it mention prerequisites or constraints such as authentication requirements.

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