Export activities as CSV

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

The description adds behavioral detail beyond the read-only and open-world annotations: one header row, one row per activity, newest-last ordering, and possible truncation. It does not contradict the annotations and usefully warns the agent to narrow the range on truncation.

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?

Two compact sentences front-load the core operation and then add format and truncation behavior without padding. Every clause carries useful information.

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?

With an output schema present and read-only/open-world annotations, the description covers the CSV shape and truncation behavior. The main gap is parameter value semantics, especially activity_type and date format, which weakens end-to-end callability.

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 descriptions are absent, so the description must compensate. It communicates that start/end define a date range, but it never explains the expected date format or what activity_type accepts, leaving the parameters underspecified.

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 names the exact operation ('Export activities in a date range as CSV'), making the resource and output format unambiguous. The CSV format distinguishes it from the activity tools, but it does not explicitly name alternatives like garmin_activities or garmin_activities_by_date.

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 explicit when-to-use or alternative-routing guidance is given; the date-range and truncation tip imply the intended use but don't exclude sibling tools. A sentence pointing to raw-activity tools for non-CSV data would make it more actionable.

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