Eight Sleep onboarding

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

Annotations already declare readOnly/idempotent/non-destructive. The description adds meaningful extra context: the flow is for non-secret data and the resulting data is stored at ~/.delx-wellness/profile.json. This gives the agent useful behavioral awareness beyond the structured hints.

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?

A single, well-structured sentence packs the purpose, usage timing, data sensitivity, and storage location into one go. No wasted words; every clause earns its place.

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 read-only, parameter-light tool, the description covers return, usage, locale scope, and data handling. It doesn't detail the exact output shape, but the absence of an output schema is low-risk because the tool's purpose is clear and an agent mainly needs to know to ask these questions.

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 description coverage is 0%, so the description must compensate, but it only clarifies locale ('en or pt-BR'). The response_format parameter is left entirely undescribed; the schema enum provides the only meaning. This is partial compensation at best.

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?

States a specific verb ('Returns'), a specific resource ('11-question onboarding flow'), and the exact target profile ('shared Delx Wellness profile'), which distinguishes it from sibling profile and data tools. It is clearly not a tautology and tells an agent exactly what this tool produces.

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?

Provides clear when-to-use guidance: 'the agent should ask these questions next so ... can personalize responses.' It doesn't explicitly name alternatives to avoid, but the onboarding context and intended follow-up action are unambiguous.

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