withings_sleep

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

With no annotations, the description carries the full behavioral burden, yet it only lists returned fields and says nothing about pagination, authentication, or what happens when the date range is empty/omitted. Since an output schema already exists, the field enumeration adds limited behavioral insight.

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 resource is front-loaded and the sentence is information-dense without filler. The long field list is somewhat heavy but each item is meaningful, so the structure is efficient overall.

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?

An output schema covers return values, but the definition is missing guidance on the two input parameters and on date-window usage. The reference to a `date` parameter that is not in the schema actively misleads, making it incomplete for a data-retrieval tool with zero annotation coverage.

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 0%, so the description must explain start_date and end_date. Instead it discusses a non-existent `date` parameter and never clarifies that the two parameters form a range or what format/direction they take, leaving both actual parameters undocumented.

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 states a specific resource (nightly sleep summaries) and enumerates its contents (time in bed/asleep, sleep stages, sleep_score, HRV), which lets an agent distinguish it from withings_devices, withings_measurements, and withings_activity. It is a noun list rather than a clear verb, but 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?

No guidance on when to call this versus withings_activity or how to use the date window. The only contextual statement ('`date` is the night's date') refers to a parameter that does not exist in the schema, and there is no mention of defaults when start_date/end_date are omitted.

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