Eight Sleep Wellness Context

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds no further behavioral details beyond creating a normalized payload, which is consistent. No contradiction, but minimal added value.

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?

Single sentence, front-loaded with verb and purpose. No wasted 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?

Description provides purpose but lacks details on how parameters affect output, what the payload contains (though output schema exists), and edge cases. Adequate but not thorough.

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 33%; only 'days' and 'timezone' have schema descriptions. The tool description does not explain any parameters, including undocumented ones like 'notes', 'soreness', 'injury_flags', 'response_format'. With low coverage, description fails to compensate.

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?

Description clearly states the tool builds a normalized payload from Eight Sleep trends for other tools, with specific verb 'build' and resource 'delx-wellness-context/v1 payload'. It distinguishes from siblings by focusing on context provision rather than raw API access.

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 the tool is for other Delx Wellness tools to read sleep context without knowing the Eight Sleep API, implying when to use. However, it does not specify when not to use or mention alternative tools like eight_sleep_get_trends.

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