download_activity_csv

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

No annotations are provided, so the description carries the behavioral disclosure burden. It explicitly states that the tool saves the CSV file and returns the file path, which is a key side effect beyond just 'downloading'. It omits details like path naming, overwrite behavior, or storage location, but the essential outcome is transparent.

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 three short sentences with the primary action front-loaded. Each sentence earns its place: what the tool does, what side effect it has, and what the returned file is useful for. There is no filler or repetition of schema data.

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?

For a single-parameter download tool with an output schema, the description covers the operation, the file-saving behavior, the returned file path, and the intended use case. It does not need to explain return values in detail because an output schema exists. Minor omissions such as file location or naming conventions do not prevent correct usage.

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 description coverage is 0%, so the description must compensate for the lack of parameter details. It only refers to 'a specific activity' and never explicitly maps the activity_id parameter to the tool's behavior, nor does it explain where the ID comes from or what format is expected. This adds almost no parameter-level meaning beyond the schema's bare title.

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 first sentence names the operation (Download), the resource (CSV file), and the target (a specific activity), clearly distinguishing it from sibling tools like download_activity_fit, download_activity_gpx, and download_activity_tcx. The mention of tabular data for spreadsheet analysis further reinforces the format-specific 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?

The description conveys a clear use context: CSV files are for tabular activity data and spreadsheet analysis. It does not explicitly name alternatives or state when not to use the tool, but among the format-specific download siblings, the intended usage is reasonably clear.

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