ebay_exchange_authorization_code

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

With no annotations, the description fully discloses behavioral traits: code auto-decoding, token storage to .env, auto-refresh every 2 hours, refresh token lifespan of 18 months, and error conditions. This provides complete transparency for safe invocation.

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 and well-structured, with a clear opening sentence, bullet-pointed important notes, and a section for common errors. Every sentence provides necessary information without 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's single parameter and no output schema, the description covers all needed context: the OAuth flow sequence, token lifecycle, error handling, and references a detailed guide. It is fully complete for an agent to use correctly.

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?

The schema already covers the 'code' parameter with a clear description. The description adds valuable context: codes can be URL-encoded and are auto-decoded, and explains how to extract the code from the redirect URL, going beyond schema basics.

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's function: 'Exchange an OAuth authorization code for access and refresh tokens.' It specifies the OAuth grant flow and distinguishes from related tools like ebay_get_oauth_url and ebay_refresh_access_token by context.

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 when to use this tool (after receiving authorization code from ebay_get_oauth_url) and provides important notes about code expiration (5 minutes) and common errors. It does not explicitly contrast with other tools but the context is clear enough for proper usage.

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