Eight Sleep onboarding

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

Annotations already indicate read-only, idempotent, and non-destructive. The description adds useful behavioral details: it returns a fixed set of 11 questions, works for a shared profile, and stores data at a specific path. No contradictions.

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 sentences with no fluff. The first sentence states what it does, the second provides usage guidance. Information is front-loaded and every sentence is essential.

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 data retrieval tool with no output schema, the description covers the return (11-question flow), scope (shared profile), and data sensitivity (non-secret). It doesn't detail the output structure, but the response_format parameter addresses formatting. Adequate for the complexity.

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 has 0% description coverage. The description adds value for the locale parameter by mentioning 'en or pt-BR', but does not explain the response_format parameter. The agent can infer from enum values, but the description misses an opportunity to clarify usage.

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 tool returns an 11-question onboarding flow for a specific profile (Delx Wellness), with language options. It specifies the purpose (personalization) and distinguishes it from sibling tools like eight_sleep_profile_get by focusing on the onboarding flow.

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 instructs the agent to ask these questions next for personalization, providing clear usage context. It doesn't explicitly state when not to use it, but the guidance is sufficient for an agent to decide.

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