ebay_display_credentials

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

The description discloses that credentials are masked and shows token status details, implying a read-only operation. Since no annotations are provided, the description carries full burden, and it adequately conveys that the tool does not modify any state, though it could explicitly state that it is non-destructive.

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 concise, consisting of two sentences. The first sentence states the primary purpose, and the second sentence elaborates with details. No unnecessary words or redundancy.

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 explains what is displayed. It lists all key pieces of information the user can expect, making it complete for the intended use case.

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?

With no input parameters and 100% schema description coverage, the description adds value by listing the specific fields displayed (client ID, masked secrets, environment, etc.). It provides meaning beyond the empty 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 clearly states it displays eBay API credentials and token information, listing specific fields like client ID, masked tokens, and expiry times. It distinguishes itself from sibling tools which are primarily for creating, updating, or deleting resources, making it clear this is a read-only informational tool.

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 explicitly says it is 'useful for debugging authentication issues and verifying configuration,' providing clear context for when to use it. However, it does not mention when not to use it or alternatives such as ebay_get_token_status for more specific token details.

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