ebay_clear_tokens

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

The description discloses the main behavioral impact: clearing tokens and requiring re-authentication. Since no annotations are provided, the description carries the full burden, and it adequately explains the destructive nature without contradictions.

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 concise sentences, no wasted words. The most important information is front-loaded, and every word contributes to understanding.

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 simplicity (no parameters, no output schema), the description covers the essential effect and outcome. It could mention if any permissions are required, but for a clear operation, it is adequately complete.

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 zero parameters, the baseline is 4. The description adds meaning beyond the empty schema by explaining what tokens are cleared and the consequence, which is sufficient.

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 specific action ('Clear all stored OAuth tokens') and includes both user tokens and client credentials, distinguishing it from other sibling tools like ebay_set_user_tokens or ebay_get_token_status.

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 this tool versus alternatives. Sibling tools like ebay_set_user_tokens or ebay_refresh_access_token exist, but the description does not explain scenarios that would favor one over the other.

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