list_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. It implies a read-only operation but does not explicitly say so, nor does it disclose pagination, ordering details, or what fields are returned. The lack of behavioral detail beyond 'most recent' leaves important information undocumented.

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 extremely concise: a single-line summary followed by clear parameter explanations with examples. Every sentence earns its place, and the structure front-loads the core purpose.

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?

This is a simple list tool with only two optional parameters, and the description covers the main purpose and parameter semantics. However, without an output schema or annotations, it does not describe the shape of the returned list (e.g., timestamps, distances), which could be useful for the agent to know. Overall it is adequate but slightly sparse.

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 provides only type and defaults with 0% description coverage in the schema itself. The description compensates well by explaining 'limit' as 'How many recent activities to return' and providing concrete examples for activity_type (running, strength_training, cycling), which adds practical meaning beyond the raw schema.

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 'List your most recent Garmin activities' with a specific verb and resource, and distinguishes from sibling tools like get_activity by focusing on listing multiple activities rather than retrieving a single one. The mention of 'most recent' also clarifies scope.

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?

The description implies usage for browsing recent activities with optional filters, but does not explicitly state when to use this instead of alternatives like get_activity or list_workouts. The context is clear enough for a simple tool, but no exclusions or alternative references are provided.

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