ebay_set_user_tokens_with_expiry

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

With no annotations provided, the description carries the full burden. It discloses the auto-refresh behavior ('can automatically refresh the access token if it's expired but the refresh token is valid'). However, it does not mention potential failure scenarios, authentication requirements, or side effects. The description adds some value but lacks comprehensive behavioral detail.

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 with two sentences, front-loading the main purpose and quickly adding key differentiators. Every sentence provides value without unnecessary verbosity.

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 5 parameters, no output schema, and no annotations, the description explains the purpose, variant, and auto-refresh behavior. However, it does not specify the return value (e.g., success/failure) or prerequisites like needing prior authorization. It is adequate but has gaps for a complex token-setting operation.

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 description coverage is 100%, so baseline is 3. The description adds context about custom expiry times and auto-refresh but does not add meaning beyond the schema descriptions, which are already clear. Thus, it meets but does not exceed the baseline.

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 verb ('Set') and the resource ('user access and refresh tokens'), and distinguishes itself from the sibling 'ebay_set_user_tokens' by mentioning it is an enhanced version that accepts expiry times and can auto-refresh.

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 provides useful context by stating 'Useful when user provides tokens that may already be partially expired,' implying the scenario for using this tool over the basic version. However, it does not explicitly state when not to use it or mention other alternatives beyond the implied basic version.

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