Get Eight Sleep User

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds the behavioral detail that the tool defaults to the authenticated user if no user_id is provided, which is valuable context beyond the annotations.

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 sentence of 14 words that efficiently communicates the action (Return), resource (profile data), and key constraint (defaults to authenticated user). No unnecessary words or repetition.

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?

With an output schema available and annotations covering safety and idempotency, the description adequately covers the core purpose and default behavior. However, it does not specify what fields constitute 'profile data,' which could help distinguish from other get tools among the 24 siblings.

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 67%, with user_id and privacy_mode well-documented. The tool description only restates the user_id default behavior already in the schema. No additional meaning is added for the other parameters (privacy_mode, response_format). Baseline 3 is appropriate.

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 Eight Sleep profile data for a specific user_id, with a default to the authenticated user. This specific verb-resource pairing distinguishes it from sibling tools like eight_sleep_get_me (which is only for the authenticated user) and eight_sleep_profile_get (likely a different endpoint).

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?

No explicit guidance on when to use this tool versus alternatives like eight_sleep_get_me, eight_sleep_get_base, or eight_sleep_profile_get. The description implies use when a specific user_id is needed, but does not state exclusions or provide comparative context.

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