oauth_v2_user_access

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

With no annotations, the description must disclose behavioral traits. It states 'Exchange', implying a side effect (token creation), but does not mention token revocation, expiration, or permission requirements. The schema shows optional parameters for PKCE and refresh, but the description adds no behavioral context beyond the basic action.

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 a single 13-word sentence, efficient and focused. It front-loads the key purpose. However, it lacks structure such as separate sections or bullet points that could improve readability for a complex OAuth tool.

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 complexity of OAuth with 7 parameters and an existing output schema (not provided), the description is too minimal. It does not explain the two-legged flow (authorization_code vs refresh_token), PKCE requirements, or error handling. The output schema exists but is not described, leaving gaps for an AI agent to safely invoke the tool.

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%, with each parameter documented. The description adds no additional meaning to parameters beyond what the schema provides, so the baseline of 3 is appropriate.

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 verifier code for a user access token, specifying version V2. It differentiates from sibling tools like oauth_access and oauth_v2_exchange by explicitly mentioning 'user access token', but does not explicitly contrast with similar OAuth token exchange 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?

The description implies usage for exchanging an OAuth code but provides no guidance on when to use this tool versus alternatives like refresh_token flow or other OAuth endpoints. No explicit when-to-use or when-not-to-use information is given.

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