zepp_heart_rate

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

The description discloses that minutes without readings are returned as null, which is useful behavioral information. However, it does not mention authentication needs, the exact structure of the summary, or any limitations, leaving some transparency gaps given that no annotations are provided.

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 short sentences and front-loads the core purpose. There is no unnecessary wording, making it highly concise and well-structured.

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?

The tool is simple with only two parameters and has an output schema, so the description adequately conveys the basic output concept. However, it does not clarify the default behavior for a null date or the effect of include_series, leaving some ambiguity for correct invocation.

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 description does not explain the 'date' or 'include_series' parameters. With 0% schema description coverage, this is a significant omission that forces the agent to infer meaning solely from parameter names and defaults, adding no semantic value beyond the schema.

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 per-minute heart rate for a single day with a summary, which distinguishes it from siblings like zepp_sleep or zepp_daily_summary. The verb is implied rather than explicit, but the resource and scope are 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 is provided on when to use this tool versus alternatives such as zepp_daily_summary or zepp_sleep. The description simply states what the tool does without any contextual usage advice or exclusions.

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