get_rest_mode_periods

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the return content but omits critical operational details: whether data is paginated (next_token suggests it is), whether authentication is required, whether it's read-only, and how start_date/end_date filter the results. These gaps are significant for an unannotated tool.

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 concise sentences that front-load the core purpose. No wasted words, though the second sentence is somewhat redundant ('Returns information about when rest mode was activated' repeats the first sentence's implication). Still, it's efficient and clear.

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?

Given no annotations, no output schema, and 0% schema coverage across three parameters, the description is incomplete. It doesn't explain pagination behavior (next_token), date range filtering, or the structure of returned episodes/tags. For a tool with these complexities and no other documentation, the description should provide more operational context.

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 0% description coverage, so the description must compensate. It mentions 'when rest mode was activated' which loosely relates to start_date/end_date but provides no format, timezone, or range semantics. The next_token parameter is entirely unexplained. The description fails to add meaningful meaning beyond the bare parameter names.

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 states a specific verb+resource: 'Get rest mode period data.' It clearly indicates what the tool returns (activation times, episodes, tags), distinguishing it from siblings like get_daily_sleep or get_personal_info. However, it does not explicitly differentiate from the one obvious sibling, get_rest_mode_period_by_id, which retrieves a single period.

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 guidance on when to use this tool versus alternatives. The description does not mention the sibling get_rest_mode_period_by_id or explain conditions for using one over the other. It only implies usage by stating what the tool returns.

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