get_daily_summary

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but the description does not clarify date behavior, defaults, authentication requirements, or any other operational constraints. It only lists returned fields rather than explaining how the tool behaves.

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 compact sentence with a front-loaded verb and a useful list of metrics. There is no filler or repetition, though it sacrifices necessary parameter information for brevity.

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 tool with one optional parameter and an output schema, the description is too thin. It omits any mention of the date parameter and provides no usage or behavior context, leaving the agent to infer too much from the tool name and schema alone.

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?

The only parameter, 'date', is completely absent from the description, while schema description coverage is 0%. The schema only provides a type and default, so the agent receives no guidance on date format, accepted values, or what omitting the date means.

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 states a clear verb and resource: 'Get activity time/goals, HR, stress, respiration, SpO2, Body Battery, steps/calories.' It enumerates the data points returned, making the tool's purpose obvious. It does not explicitly contrast with sibling tools such as get_stress or get_body_battery, but the 'daily summary' framing implies an aggregate view.

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?

There is no guidance on when to use this tool versus the many sibling tools that cover individual metrics. It does not mention alternatives, exclusions, or scenarios where a different tool would be more appropriate.

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