Setup Garmin Credentials

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

The description discloses key behavioral traits: encryption at rest, immediate login, and no plaintext password writes. Annotations include openWorldHint and destructiveHint, and the description elaborates safely without contradicting them, though it could mention any overwrite/rotation of existing credentials.

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 short sentences deliver purpose, timing, and security context. Everything is front-loaded and relevant, with no filler.

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 two-param, no-output-schema tool with helpful annotations, the description covers why, when, and the security model. It could go one step further by clarifying the response/error behavior or that it will overwrite/replace existing credentials, but overall it's sufficiently complete.

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 100%, and each parameter already has a clear description ('Garmin Connect account email/password'). The tool description adds no extra semantic detail to the parameters, so the baseline of 3 is appropriate.

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?

Purpose is crystal clear: store Garmin credentials in the OS native vault and log in immediately. It names the specific resource (Garmin credentials), the action (setup/store), and the immediate consequence (login), distinguishing it from siblings like check_credentials and clear_credentials.

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 states when to use this tool: 'Use this when the server reports that credentials are missing or invalid.' It doesn't explicitly call out when not to use it or mention alternatives, but the trigger condition is concrete and sufficient for selection.

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