garmin_daily_events

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

No annotations are provided, so the description carries the full burden, yet it only states the data category. It says nothing about how many days are returned, ordering, pagination, auth requirements, or any behavioral limits beyond the example types.

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?

One front-loaded sentence with no filler; every clause earns its place by naming the resource and giving examples.

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?

An output schema exists, so return values need not be described, and the tool is simple with one optional parameter. However, with no annotations and zero parameter documentation, the description should have covered the 'days' window to be fully actionable.

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 single parameter 'days' has 0% schema description coverage (only a default of 7), and the description never mentions it. An agent cannot learn from either source what 'days' controls or its valid range.

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?

Names the resource ('Daily events detected by your Garmin') and clarifies it with concrete examples (stress spikes, body battery events), so an agent knows it returns a curated event list rather than raw metrics. It does not distinguish itself from overlapping siblings like garmin_stress or garmin_body_battery, which the examples partially collide with.

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 explicit when-to-use guidance and no mention of alternatives, despite close siblings (garmin_stress, garmin_body_battery, garmin_today) that an agent could confuse it with. Usage is only implied by the 'daily events' framing.

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