Withings Sleep Summaries

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds that the tool requires a scope and is not medical advice, but does not disclose additional behavioral traits such as pagination limits, privacy mode defaults, or how dates are handled. With annotations providing baseline safety, a score of 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?

The description is two sentences long, covers the essential purpose and requirement, and contains no redundant or irrelevant information. It is front-loaded with the key action.

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?

Despite the schema covering many parameters and an output schema existing, the description fails to mention pagination behavior, privacy mode options, or what 'common sleep fields' actually includes. The tool has eight parameters and complex behavior, but the description is too minimal to fully guide an agent on correct invocation and interpretation of results.

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%, meaning almost all parameters have detailed descriptions in the schema. The tool description does not add any further semantic information about parameters beyond the schema. Baseline is 3 when coverage is high, and no extra value is provided.

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 verb 'List', the resource 'Withings sleep summaries', and specifies 'with common sleep fields', which distinguishes it from sibling tools like withings_list_sleep that may offer different data. The purpose is unambiguous.

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 the required scope ('user.activity') and provides a disclaimer ('Not medical advice'), giving some context for appropriate use. However, it does not explicitly state when to use this tool versus alternatives (e.g., withings_list_sleep for a different sleep summary), nor does it mention limitations or exclusions.

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