polar_exchange_authorization_code

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds that the tool returns POLAR_ACCESS_TOKEN and POLAR_USER_ID, which clarifies the side effect (obtaining credentials). It does not mention rate limits or failure modes, but the annotation and description together provide adequate transparency.

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 succinct, using two sentences to convey the core action, output, and purpose. There is no redundant or extraneous 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?

Given there is no output schema, the description compensates by stating the return values (POLAR_ACCESS_TOKEN and POLAR_USER_ID) and their role in configuration. It lacks details about error handling or prerequisites, but for this straightforward exchange operation, the provided context is sufficient.

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 complete (100%) and each parameter has a description, so the schema already conveys the semantics. The description does not add extra parameter context, maintaining the baseline of 3.

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 action (exchange) and the resource (OAuth authorization code) and the outcome (access token). It distinguishes this tool from siblings because it is the only one that performs this exchange, while polar_get_authorization_url generates the URL for obtaining the 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?

The description implies usage after receiving an authorization code and explicitly mentions that the returned token and user ID are needed to configure the MCP server, giving clear context. It does not explicitly mention alternatives, but the sibling polar_get_authorization_url makes the flow obvious.

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