Withings Sleep Summaries

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is safe and idempotent. The description adds context about required scope and a disclaimer, but does not describe pagination behavior, rate limits, or the nature of summaries versus raw data. With annotations covering safety, a 3 is appropriate.

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 zero wasted words. First sentence states the purpose; second adds essential context (scope requirement, disclaimer). Front-loaded and efficient.

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?

Given the tool has 8 parameters, an output schema, and annotations covering safety, the description is mostly complete. It could briefly mention that 'sleep summaries' differ from raw sleep data (as in 'withings_list_sleep') to improve clarity, but it is adequate.

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 88% (7 of 8 parameters have descriptions in schema). The tool description does not add any parameter-level information beyond what the schema provides. Baseline 3 is correct since the schema already documents parameters thoroughly.

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 'List Withings sleep summaries with common sleep fields.' It specifies the verb (list) and resource (sleep summaries). However, it does not explicitly distinguish itself from the sibling tool 'withings_list_sleep', which might cause confusion.

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 mentions 'Requires user.activity scope' and 'Not medical advice,' but does not provide guidance on when to use this tool versus alternatives like 'withings_list_sleep' or 'withings_list_activity'. No explicit when-to-use or when-not-to-use guidance.

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