get_daily_sleep

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety behavior is covered. The description adds that parameters and date restrictions follow the official interface, but it never specifies what those restrictions are, leaving the agent with an opaque pointer rather than actionable behavior.

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 short but contains redundant phrasing across Chinese and English ('单晚睡眠' and 'Return daily sleep data for a calendar date') plus non-actionable meta about matching the official client. It is not excessively long, but not every sentence earns its place.

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?

With no output schema and no schema parameter descriptions, the description should explain the date format and what sleep data is returned. Instead it only says data is returned for a calendar date and defers constraints to the 'official interface,' leaving key invocation details unspecified.

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 compensate. It mentions 'calendar date' and 'date restrictions' but gives no format, timezone, allowed range, or constraint details for the single required parameter.

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 and scope: '单晚睡眠' / 'Return daily sleep data for a calendar date.' It distinguishes itself somewhat from summaries by emphasizing a single night, though it does not explicitly contrast with get_daily_sleep_summaries.

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?

There is no explicit guidance on when to use this tool versus alternatives such as get_daily_sleep_summaries or other daily metric tools. Use is only implied by the phrase 'daily sleep data for a calendar date.'

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