ebay_display_credentials

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

No annotations provided, so description carries full burden. It discloses that credentials are masked and token status including expiry times are shown. Does not explicitly state whether the tool is read-only or if it modifies state, but the verb 'display' implies no side effects.

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?

Two sentences: first states purpose, second details output and use case. No filler words or repetition. Highly efficient.

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?

No output schema, but description lists all significant output fields (client ID, client secret masked, environment, redirect URI, token status, expiry times). Could mention return format (JSON) but still sufficient for a display 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?

No parameters exist (0 params, schema coverage 100%). Baseline is 4 as no additional documentation is needed. Description does not add parameter info but is not required to.

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?

Description uses specific verb 'display' and resource 'eBay API credentials and current token information', listing exact items shown. Clearly distinguishes from sibling tools which handle campaign management, inventory, etc.

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?

States it's 'useful for debugging authentication issues and verifying configuration', providing clear context. Does not explicitly exclude other tools, but sibling tools are unrelated, so differentiation is implicit.

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