ebay_search

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

With no annotations, the description carries full burden for behavioral disclosure. It fails to mention rate limits, authentication workflow (though client_id/client_secret are in schema), pagination behavior, or any side effects. The description is too brief to inform the agent about safety 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?

The description is a single concise sentence, front-loaded with the core action. However, it is too brief, sacrificing completeness for brevity. It does not earn its place by providing essential guidance that the schema lacks.

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 multiple sibling tools, the description is inadequate. It fails to explain search behavior, filter usage, pagination, or result format. The agent would lack sufficient context to use the tool effectively.

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 description coverage is high (89%), so the schema itself explains most parameters. The description adds no extra meaning beyond listing the action. Baseline of 3 is appropriate as it neither improves nor detracts from the schema.

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 states 'Search eBay listings via the Browse API', clearly specifying the action (search) and resource (eBay listings). It is specific but does not distinguish itself from sibling tools like ebay_get_item or ebay_get_categories, which would warrant a 5.

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 is provided on when to use ebay_search versus alternatives. The description does not mention any context, prerequisites (beyond the required parameters), or situations where other tools would be more appropriate.

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