garmin_recent_activities

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. It does convey that output is summary-level, recent activity data, which implies a read-only listing operation. It does not describe ordering guarantees, empty-result behavior, or whether activity_type filters before/after applying the limit, but the simple read-only nature and output schema reduce the risk.

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 short, front-loaded sentence with no wasted words. Both 'most recent' and 'compact summaries' add meaningful scoping, and it does not repeat the tool name or restate schema fields.

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?

The input schema fully documents the two parameters, and an output schema exists, so return-value details do not need to be spelled out. The main gap is lack of guidance for choosing this over the many activity-related siblings, but for a simple list tool the core information is present.

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%: both limit and activity_type already have descriptive text, including defaults, range, and an example type key. The tool 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 clearly identifies the resource ('most recent activities') and the output form ('compact summaries'), so an agent can tell this returns a list of recent activity summaries. It lacks an explicit verb like 'retrieve' or 'list' and does not explicitly distinguish it from garmin_activities_by_date or garmin_activity, but the meaning is unambiguous.

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?

Usage is only implied: 'most recent activities' suggests this tool is for quickly viewing recent activity summaries. However, it never tells the agent when to prefer this over garmin_activities_by_date, garmin_activity, or garmin_today, nor does it state any exclusions. With many siblings, more explicit routing would help.

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