export_coros_backup

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds useful context that credentials are not included and the output is JSON, but it does not disclose auth prerequisites, pagination behavior, or how workoutLimit affects results.

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 concise and front-loaded with the core action, resource, and output format. The second sentence adds a relevant exclusion. It is slightly sparse but contains no filler or wasted words.

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 no output schema and zero parameter documentation, the description leaves too much to guesswork: date formats, limit semantics, output structure beyond 'JSON', and whether authentication is required. It is minimally adequate as a label but not as invocation guidance.

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%, and the description does not mention startDate, endDate, or workoutLimit at all. The agent gets no guidance on date format, inclusiveness, timezone handling, or how workoutLimit caps the export, so parameter meaning is entirely undocumented.

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 states a specific verb and resource: 'Export COROS workout-library metadata and raw calendar data as JSON.' It also scopes the purpose to backup/inspection and explicitly excludes credentials, making it clearly distinguishable from sibling read/export 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?

The phrase 'for backup or inspection' gives a clear context for when to use this tool. However, it does not name alternatives like get_activity_export_url or coros_read, nor does it state when NOT to use this tool, so the guidance is implied rather than explicit.

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