zepp_sleep

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

With no annotations, the description must carry the behavioral transparency burden. It discloses the output fields but does not mention read-only nature, date format or timezone handling, potential limitations, or any side effects. The description primarily repeats what the output schema likely contains, adding little beyond that.

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 a single, front-loaded sentence that names the resource and immediately lists the output fields. Every word earns its place, with no filler or redundancy. This is a model of conciseness.

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?

While the output fields are well described, the essential 'date' parameter is left completely unexplained. Given the tool has only one parameter and no annotation coverage, the description should have clarified how to select the night (e.g., date format or timezone). The output schema exists but the input side is under-specified.

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 input schema has one 'date' parameter with 0% description coverage, and the tool description completely omits any mention of how to specify the date. No format, default behavior, or optionality is explained beyond the schema's bare structure. The description adds zero value for parameter understanding.

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 resource is sleep data for a single night and enumerates the specific metrics returned (light, deep, REM, awake minutes, sleep score, resting heart rate). It distinguishes itself from siblings by focusing on 'single night' breakdown, though it lacks an explicit verb like 'get' or 'retrieve'.

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 phrase 'for a single night' implies the tool is meant for per-night sleep details, giving some usage context. However, there is no explicit mention of when to use this over alternatives like zepp_daily_summary or zepp_heart_rate, nor any exclusion criteria.

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