Revoke Strava OAuth Access

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

Description discloses that it deletes the local token file, adding context beyond the destructiveHint annotation. However, it does not mention irreversibility or effects on ongoing sessions.

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 short sentences, no redundant information, front-loaded with action and condition.

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?

Simple tool with output schema and annotations; description covers purpose and usage. Could mention what happens after revocation (e.g., data remains but connection severed), but overall sufficient for a clear action 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?

The only parameter (response_format) is not described in the tool description. With 0% schema description coverage, the description should provide guidance on this parameter, but it does not.

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?

Description clearly states the tool revokes Strava OAuth access and deletes the token file. This is a specific verb+resource combination, distinct from all sibling tools which cover different actions.

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 says 'Use only when the user explicitly wants to disconnect Strava', providing clear usage conditions and no ambiguity.

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