Eight Sleep profile update

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

Beyond annotations (which indicate idempotent and non-destructive), the description reveals specific behavioral traits: persistence to a file, rejection of credential-like fields, and the requirement for explicit user intent. This adds value for safe invocation.

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 sentences, each earning its place: purpose, usage requirement, and security constraint. Front-loaded with the action. 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?

The description covers the update action, user intent requirement, and credential filtering, but omits return value or error behavior. Given no output schema, this information would help an agent understand what to expect after invocation.

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?

The description adds significant meaning for the main `patch` parameter by explaining it is a partial patch and detailing credential rejection patterns. It also reinforces the `explicit_user_intent` parameter. Despite 67% schema coverage, the description compensates with critical semantic details.

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's action: 'Persist a partial patch to the shared Delx Wellness profile'. It uses specific verb (persist) and resource, distinguishing it from sibling tool eight_sleep_profile_get which retrieves the profile.

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 provides a key usage condition ('Requires explicit_user_intent: true') and warns against credential fields, but does not explicitly mention when to use this tool versus alternatives like eight_sleep_profile_get or other sibling tools.

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