get_sleep_summaries

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile and data-freshness expectation are covered elsewhere. The description adds only one behavioral fact, 'nightly', which tells the agent the granularity is one summary per night; it says nothing about pagination, coverage limits, or what happens with missing data.

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?

Two short sentences, front-loaded with the verb and resource, with no filler. Both sentences contribute, though the second is terse enough that it borders on uninformative rather than being wasteful.

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?

For a two-parameter read-only tool with annotations and no output schema, the definition covers purpose and scope adequately. The main remaining gaps are date formatting and the optionality semantics of end_date, which are small but non-trivial 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?

Schema description coverage is 0%, so the description carries real weight here and it does partially compensate by framing the two parameters as a 'date range'. However, it never states the date format, that start_date is required while end_date is optional, or what the default end date means when omitted.

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?

States a specific verb and resource ('Get nightly sleep summaries') plus a scope ('for a date range'), which is clear for an agent. It does not explicitly differentiate itself from the closest siblings, get_sleep and get_daily_summary, so sibling disambiguation is left to inference.

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?

'Best for sleep trends' gives a weak use-case hint that implies this is the aggregate/trend-oriented option versus raw sleep retrieval. There is no explicit when-not guidance and no named alternative such as get_sleep, so the routing signal is only implied.

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