get_daily_activity

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

With no annotations, the description carries the full burden, but it only lists return fields. It does not disclose behavior such as default date handling, timezone considerations, or any limitations. The existence of an output schema reduces the need to explain return values, but the description lacks behavioral context.

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 sentence that is front-loaded and free of fluff. It conveys the core purpose efficiently, though it under-specifies details.

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 simplicity of the tool (one optional parameter, output schema present), the description still leaves critical gaps: no mention of the date parameter, no distinction from timeseries, and no guidance on expected input. The sentence is too terse for an agent to invoke correctly without additional assumptions.

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 0% and the description does not mention the 'date' parameter at all. The agent receives no guidance on the accepted date format, the meaning of null, or how the parameter affects results. With one parameter and zero coverage, the description must compensate but fails to do so.

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 the tool's function with a specific verb ('Get') and resource ('daily activity summary'), and enumerates the return fields (steps, calories, distance, active minutes). The term 'summary' distinguishes it from the sibling 'get_activity_timeseries', which implies time-series data.

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?

No guidance is provided on when to use this tool versus alternatives like get_activity_timeseries. The description does not mention any prerequisites, exclusions, or specific contexts where this summary is preferred.

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