get_daily_activity

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It lists return fields but does not mention pagination/truncation behavior, timezone handling, authentication requirements, or any other operational traits. As a read-only getter, the lack of side-effect warnings is less critical, but the description still leaves behavioral details to the schema.

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 a single dense sentence with no filler or repetition. It front-loads the tool's purpose and then efficiently lists the returned metrics, making it easy to scan.

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 that an output schema exists and all parameters are fully documented in the input schema, the description is largely complete for a simple read-only getter. It clearly states what data is returned, though it could add a note about pagination or authentication prerequisites.

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 100%, so the schema fully documents all four parameters, including defaults and the purpose of include_time_series. The description adds no parameter-level meaning, so the baseline of 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 uses a specific verb and resource ('Get daily activity') and enumerates the exact metrics returned (activity score, steps, calories, distance, activity times, MET minutes, inactivity alerts). This clearly distinguishes it from sibling tools focused on sleep, stress, readiness, or workouts.

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 this tool is for retrieving daily activity metrics, but it does not explicitly state when to use it over alternatives like get_daily_summary or get_workouts, nor does it mention any exclusions or prerequisites.

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