get_garmin_activities

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

With no annotations present, the description carries full burden for behavioral disclosure. It only mentions the parameter limit (max 50), but fails to disclose effects like requiring prior authentication, rate limits, or error behavior (e.g., if no activities found).

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 very concise (one sentence plus parameter note) and front-loads the core purpose. However, it lacks structure such as separate sections for arguments or examples, but is appropriately minimal for a simple tool.

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?

Despite having only one parameter and an output schema, the description does not explain the output structure, authentication dependency (given 'authenticate' sibling), or error scenarios. It provides minimum viable information but leaves gaps for an agent to infer.

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 description provides meaning for the single parameter 'nb' beyond the schema, specifying it controls the number of activities with default 10 and max 50. Since schema description coverage is 0%, this addition improves usability, though it remains brief.

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 'Récupère' and resource 'activités Garmin Connect', specifying it retrieves the latest activities. However, it does not explicitly differentiate from sibling tools like 'get_recent_activities', which may have similar purpose.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives, nor does it mention prerequisites like authentication with the 'authenticate' sibling tool.

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