garmin_activities

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

No annotations provided, so description carries full burden. It does not disclose pagination, authentication needs, rate limits, data freshness, or response format. Only states basic functionality.

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?

Very concise: one sentence for purpose then structured Args list. No unnecessary words, front-loaded with key info. Efficient.

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?

Describes parameters adequately but missing output schema (return fields) and any behavioral notes. For a list tool with 4 params, it covers the basics but lacks completeness on what the agent gets back.

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 coverage is 0%, but description adds defaults (start_date defaults to 7 days ago, end_date to today, limit to 10) and enumerates activity_type values. This adds meaning beyond the schema's titles.

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?

Description clearly states 'List recent activities filtered by date range and type' with a specific verb and resource. It distinguishes from siblings like garmin_activity_detail (likely detail view) and other non-activity tools.

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?

Implies usage for listing and filtering activities, but provides no explicit when-to-use, when-not-to-use, or alternatives among siblings. The context is clear but lacks guidance.

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