Revoke Polar OAuth Access

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

Annotations already label it as destructive and not read-only. The description adds that it deletes a local file, which is consistent but does not disclose further behavioral traits like reversibility or side effects.

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?

Two sentences efficiently convey the purpose and usage with no extraneous content. Front-loaded with the verb 'Delete'.

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 destructive nature and having an output schema (context), the description is adequate for purpose and usage but fails to explain the response_format parameter, leaving a completeness gap.

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 0%, and the description does not mention the only parameter (response_format). The tool cannot be used correctly without understanding this parameter, which is a critical omission.

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?

Clearly states the action ('Delete the local Polar token file') and the context ('when the user explicitly wants to disconnect this MCP'). Distinguishes from sibling tools by specifying a unique operation.

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 tells when to use ('only when the user explicitly wants to disconnect this MCP') and mentions an additional step ('revoke the remote grant from Polar if needed'), providing clear guidance.

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