garmin_recent_activities

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It states it lists activities but does not mention that it is read-only, requires authentication, or what 'raw' means. Behavioral traits are minimally disclosed.

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 and very concise. While brevity is good, it lacks structural elements like bullet points or separate sections that could improve clarity.

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 tool has an output schema and two parameters, but the description does not explain the return format, the meaning of 'raw' vs processed activities, or the pagination mechanism. It is incomplete for the given complexity.

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 input schema has two parameters (limit, start) with zero description coverage. The tool description does not mention the parameters or clarify their meaning (e.g., pagination). The description fails to add any value beyond the schema's default values.

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 action ('List') and the resource ('raw private recent Garmin activities'), giving a specific purpose. It distinguishes from siblings like 'garmin_activity' (likely for a single activity) and 'garmin_daily_stats'. However, 'raw' and 'recent' are slightly ambiguous without further context.

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 'garmin_activity' or 'garmin_daily_stats'. The description lacks any 'when-to-use' or 'when-not-to-use' information.

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