ebay_set_user_tokens

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

With no annotations, the description discloses key behaviors: tokens are persisted to disk and automatically refreshed. It also notes rate limit benefits. It doesn't mention overwriting existing tokens or potential side effects, but the covered aspects are valuable.

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?

Three sentences with clear front-loading: purpose, source, then behavior/benefit. No redundant words; each sentence adds essential information.

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?

For a simple 2-parameter tool with no output schema, the description covers purpose, token source, persistence, auto-refresh, and rate limit advantage. Minor omission: could state that it overwrites existing tokens, but overall 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?

Schema coverage is 100%, so baseline is 3. The description adds context about obtaining tokens via OAuth and the lifecycle (persistence, auto-refresh), which goes beyond the schema's parameter descriptions.

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 sets user access and refresh tokens for authenticated API requests, distinguishing it from sibling tools like ebay_clear_tokens, ebay_refresh_access_token, or ebay_set_user_tokens_with_expiry. The verb 'set' and resource are specific.

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 explains tokens should be obtained via OAuth and highlights higher rate limits compared to client credentials, which helps in deciding when to use. However, it does not explicitly mention when not to use it or compare with similar tools like ebay_set_user_tokens_with_expiry.

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