Exchange Fitbit OAuth Code

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

Discloses that tokens are stored locally with 0600 permissions and never returned, adding behavioral context beyond annotations that only indicate non-read-only and non-destructive.

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?

Three sentences with no wasted words, front-loading the purpose and then adding behavioral and usage constraints.

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?

Covers purpose, behavior, security, and user involvement, sufficient for an authentication tool with annotations and output schema present.

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 already describes 'code' parameter as an authorization code or redirect URL; description adds no further parameter-specific detail. Baseline 3 with schema coverage approximately 50%.

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 'Exchange a Fitbit OAuth authorization code for local tokens,' specifying the action and resource. Distinguishes from sibling data retrieval and other 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?

Explicitly requires explicit user action and warns agents not to invent codes, providing clear when-to-use and when-not-to-use guidance.

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