get_daily_activity

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

With no annotations, the description fully bears the transparency burden. It states the tool is read-only, returns an empty payload for days without synced data, and implies no side effects. The schema description additionally warns about date constraints, but the tool description does not mention rate limits or response structure.

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 three sentences with no unnecessary words. It front-loads the primary purpose and efficiently covers sample content, edge case, alternative, and requirements.

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?

For a simple tool with one parameter and no output schema, the description covers purpose, sample contents, edge case, sibling alternative, and requirements. However, it omits details about the response format or fields, which would be helpful given the lack of 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 100%, and the schema already provides a detailed description for the 'date' parameter including format, pattern, and sync behavior. The tool description adds little new about the parameter, only that it expects a single day. Baseline 3 is appropriate.

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 it returns 24/7 activity time-series samples for one calendar day. It specifies the API source, sample contents (timestamp, steps, HR), and edge case (empty payload). This distinguishes it from sibling tools like list_daily_activity (date range) and get_daily_activity_statistics (statistics).

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 explicitly says 'Use list_daily_activity to fetch a date range,' providing a clear alternative. It also mentions the requirement for a subscription and that days without data return an empty payload, but does not elaborate on when to use other siblings like get_daily_activity_statistics.

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