fitbit_get_sleep

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

No annotations provided, so description fully owns behavioral disclosure. It explains cache vs live behavior, data sparsity, and return structure (one entry per night with fields).

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?

Description is well-structured with clear sections and reasonable length. Could be slightly more concise, but every sentence adds value.

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?

Output schema exists, but description already details return fields. The description is complete for the tool's complexity, covering parameters, behavior, and output.

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 coverage is 0%, but the description thoroughly explains all three parameters (start_date, end_date, live) with formats, defaults, and behavior, adding significant meaning beyond the schema.

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 that the tool gets nightly sleep data (duration, stages, efficiency), distinguishing it from sibling tools like fitbit_get_activity and fitbit_get_heart_rate.

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?

Provides clear guidance on default cache usage, live fetching, and prerequisites like fitbit_sync. Mentions data sparsity. Lacks explicit when-not-to-use scenarios, but overall well-constructed.

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