ebay_exchange_authorization_code

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

No annotations provided, so description fully carries behavioral disclosure. Reveals automatic token storage and usage, code expiration (~5 minutes), URL decoding, .env file saving with auto-refresh every 2 hours, and refresh token duration (18 months). No 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?

Well-structured with sections, important notes, and common errors. Length is justified by the needed detail for OAuth flow; no 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?

For a single-parameter tool with no output schema, the description is complete. Covers the full OAuth flow, token handling, error scenarios, and references a documentation file. No gaps.

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?

Single parameter 'code' has schema description 'The authorization code received from eBay after user authorization'. Description adds extraction details, URL-encoding, and expiration context, going beyond schema. High schema coverage (100%) means baseline is 3, but added value justifies 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?

The description clearly states the tool exchanges an OAuth authorization code for access and refresh tokens, completing the OAuth 2.0 Authorization Code grant flow. It distinguishes itself from sibling tools as the only OAuth token exchange tool among many eBay API tools.

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?

Explicitly describes when to use (after user authorization and receiving code) and how to extract the code from the redirect URL. Includes common errors with troubleshooting guidance. Does not explicitly state when not to use, but context is sufficient.

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