Eight Sleep Connection Status

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

Annotations already indicate readOnly and idempotent, but the description adds critical safety info: it does not call Eight Sleep and does not expose secrets. This goes beyond what annotations provide.

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 concise sentences, each adding unique information. The first lists what is checked, the second adds safety guarantees. No unnecessary words.

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?

While an output schema exists, the description does not hint at what the output contains (e.g., a status summary). For a diagnostic tool, explaining the output format would improve completeness. Adequate but lacks detail.

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%, yet the description does not explain the two parameters (client and response_format). These are important for controlling output format and client-specific behavior, so the missing explanation is a significant gap.

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 it checks multiple configurations (env, local config, token file, Node version, privacy mode, mutation gate) and explicitly says it does not call Eight Sleep or expose secrets. This distinguishes it from sibling tools that likely perform API calls or data operations.

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 implies use for debugging or setup but does not explicitly state when to use it versus alternatives. It provides context but lacks exclusions or when-not guidance.

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