ebay_refresh_access_token

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

Discloses the action (refresh) and return values (new token and expiry). Lacks detail on side effects like old token invalidation or rate limits. No annotations provided, so description bears full burden.

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 covering purpose, usefulness, and prerequisites. No wasted words, front-loaded with key 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?

Covers what the tool does, when to use, prerequisites, and return values. No output schema exists, so description compensates well. Could mention that it updates the stored token state.

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?

Input schema has zero parameters, so description does not need to add parameter info. Schema coverage is 100% trivially. Baseline for 0 params is 4.

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?

Clearly states 'Manually refresh the user access token using the stored refresh token', specifying the verb and resource. Distinguishes from siblings like ebay_get_token_status and ebay_exchange_authorization_code.

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 when to use (proactive refresh, recovering from auth errors) and prerequisites (tokens set via .env or ebay_set_user_tokens_with_expiry). Does not explicitly list alternative tools for token management.

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