Fitbit Activity Logs

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

Annotations already indicate read-only, non-destructive, idempotent behavior. The description adds that it 'Requires activity scope' and supports privacy modes, which is helpful but does not significantly expand beyond annotations. No contradictions.

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 extremely concise: two sentences that front-load the core purpose and key features. Every part is essential and adds value without redundancy.

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 the presence of an output schema, the description adequately covers the tool's purpose and key aspects (cursor, pagination, privacy, scope). It could be more complete by linking to siblings, but the output schema fills the return value gap. Sufficient for a list tool.

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 88%, so the schema already explains most parameters (e.g., after, before). The description's mention of 'before/after cursor, pagination' aligns with schema but adds no new semantic meaning beyond what is documented in 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 'List Fitbit activity logs,' specifying a concrete verb and resource. It distinguishes from siblings like 'fitbit_get_activity' (single activity) and 'fitbit_get_activity_day' (daily summary) by implying a list operation.

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 mentions supports for cursor, pagination, and privacy modes, providing usage context. However, it lacks explicit guidance on when to use this tool versus alternatives like 'fitbit_get_activity' or 'fitbit_list_sleep'. No when-not-to-use or alternatives are mentioned.

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