Fitbit Sleep Logs

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds 'Requires sleep scope' and 'Not medical advice', which are minor. No contradiction. For a read-only tool, the behavioral context is sufficient but not enhanced beyond annotations.

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?

Three sentences: purpose, features, requirement. Front-loaded and efficient. Could be slightly more structured, but no waste.

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 9 parameters, high schema coverage, and an output schema, the description covers key aspects (cursors, pagination, privacy, scope). Missing details on explicit_user_intent and response_format are minor given the structured schema and output schema.

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 high (89%), so baseline 3. Description groups parameters as 'before/after cursor, pagination and privacy modes', providing a high-level overview but not adding significant detail beyond schema descriptions.

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 'List Fitbit sleep logs', a specific verb+resource. It mentions features like cursor, pagination, privacy modes, distinguishing it from siblings like fitbit_get_sleep_day (single day).

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?

The description implies listing vs single-day via features but lacks explicit when-to-use or when-not-to-use. 'Requires sleep scope' is a prerequisite, but no exclusion criteria or alternatives are given.

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