zepp_daily_summary

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions sleep breakdown into stages, which is useful, but does not state whether this is read-only, require auth, or clarify behavior like date range defaults or timezone handling. The absence of any side-effect or permission context limits transparency.

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, front-loaded with the main output metrics, and adds a useful detail about sleep breakdown. Every word provides relevant information without redundancy.

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 has an output schema and sibling tools, so the description doesn't need to detail return values. It covers the basic purpose and sleep granularity, but lacks parameter semantics and fails to explicitly differentiate usage from zepp_sleep. It is adequate for a simple summary but not fully comprehensive.

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 schema has 2 parameters (from_date, to_date) with 0% description coverage. The description only says 'for a date range' and does not explain date formats, inclusivity, or that both parameters are optional with null defaults. The parameter names are self-explanatory, but the description adds little beyond what the schema property names already imply.

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 identifies the tool's output: daily steps, distance, calories, and sleep for a date range. It distinguishes from sibling zepp_sleep by explicitly including sleep as one component among broader metrics, though it lacks a direct 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 description implies the tool is used for a daily summary of multiple metrics, but provides no explicit guidance on when to choose this over zepp_sleep or other siblings. It does not state exclusions or alternatives, leaving the agent to infer usage from the listed data fields.

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