Revoke Fitbit OAuth Access

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

The description adds value beyond annotations by specifying that OAuth grant is revoked and a local token file is deleted. Annotations already indicate destructiveHint=true, so no contradiction. The description provides concrete details about what gets destroyed.

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: first defines the action, second specifies when to use. No unnecessary words, front-loaded with the core purpose.

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 simple revoke operation with annotations and an output schema, the description is nearly complete. It lacks mention of the response_format parameter and side effects, but the essential behavior and usage condition are clear.

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 description does not mention the single parameter (response_format) at all. Schema description coverage is 0%, so the description should compensate but fails to do so. The parameter controls output format, which is not trivial for an agent to infer.

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 ('Revoke the current Fitbit OAuth grant and delete the local token file') and the resource (OAuth grant and token file). It distinguishes from sibling tools, as no other tool performs revocation; other tools handle authorization setup or data retrieval.

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 explicitly states when to use: 'Use only when the user explicitly wants to disconnect Fitbit.' It does not mention when not to use or provide alternatives, but the explicit condition is sufficient for most use cases.

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