Check eBay configuration

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

The annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds important behavioral context: 'make one live test call to confirm the credentials work.' This clarifies that despite being read-only, the tool performs an actual network call to the eBay API for testing, which is beyond the basic read-only label. It also implies credential validation, adding value over the annotations.

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: two sentences, with the purpose front-loaded and the usage guidance immediately after. No wasted words, and it covers purpose, behavior, and usage in a compact form.

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 no parameters and no output schema, the description fully covers what an agent needs to know: what it does (reports config, tests credentials), when to use it (after a failed search), and the side-effect (live call). It is complete for its simplicity.

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?

There are no parameters in the schema, so the baseline is 4. The description does not need to explain parameters since none exist. It adequately explains the tool's behavior without needing parameter-level detail.

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's purpose: 'Report how eBay is configured and make one live test call to confirm the credentials work.' This is a specific action (report/test) on a specific resource (eBay configuration), and it distinguishes itself from sibling tools like search_ebay and get_listing_details by focusing on connection/credential verification rather than data 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 gives explicit when-to-use guidance: 'Run this first whenever a search fails or returns nothing.' This is a clear trigger condition that indicates precedence over sibling tools. However, it does not explicitly mention when not to use it or list alternative tools, so it falls short of a 5.

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