get_sleep

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no statement that this is a read-only query, no windowing/pagination behavior, no note that 'days' defaults to 14. Without annotations, the near-total absence of behavioral context is a real gap.

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?

It is a single short sentence with no filler, so it is efficient, but it is under-specified rather than genuinely concise. There is no front-loaded statement of purpose for the field list to elaborate on.

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?

An output schema already exists, so enumerating returned metrics is largely redundant, while the actually useful information ('days' semantics, default window, read-only nature) is missing. For a tool with a parameter and no annotations, the description is too thin to call it complete.

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 single parameter 'days' has 0% schema description coverage and a default of 14 that is never surfaced in the description. The description does not mention the parameter at all, so an agent gets no meaning for the time-range control beyond the bare name.

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 is a noun fragment listing returned fields ('Sleep sessions with stage minutes, efficiency, need, performance, debt, consistency') rather than a verb+resource statement. An agent can infer retrieval of sleep data, but the fragment never says what the tool does or over what scope. It also gives no differentiation from siblings like get_daily or get_report.

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 when-to-use guidance, no prerequisites, and no mention of alternative tools. Siblings such as get_daily, get_heart_rate, and get_report plausibly overlap with sleep data, yet the description never routes the agent between them.

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