garmin_recent_overview

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds the behavioral trait that data is 'cached', implying it may not be live and could require a sync via garmin_sync, which is valuable context beyond the annotations.

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, front-loaded sentence that efficiently conveys the core purpose. No unnecessary words or repetition, and every phrase adds meaning.

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?

While the description is brief, it covers the basic function for a simple read-only tool with rich annotations and an output schema. However, it does not clarify what 'cached' means in practice (e.g., staleness, sync implications) or how the response combines trends and activities, leaving some contextual gaps.

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 only loosely references 'most recent number of days' without explaining that the 'days' parameter controls the window or that it defaults to 7. For a single optional parameter, the description does not sufficiently compensate for the lack of schema documentation.

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 verb 'Return' and resource 'cached trends and activities' with a time scope of 'most recent number of days'. It distinguishes from siblings like garmin_get_trends and garmin_list_activities by indicating a combined overview of both trends and activities, though it does not explicitly name alternatives.

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 guidance on when to use this tool versus siblings. The description only states what it returns, but does not mention when to prefer this over garmin_get_trends or garmin_list_activities, nor 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.