get_workout_fit

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

Explains read-only nature, default output content, and size implications of full mode. Also notes that workoutKey is not guessable. Good coverage without annotations.

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?

Concise, well-structured with main action first. Each sentence adds necessary information without redundancy. No 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?

No output schema, but description adequately explains return shape for both modes. Covers key aspects for agent to decide invocation.

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 covers 100% of parameters. Description adds valuable context: workoutKey must be discovered via list_workouts, and full parameter effect is clarified beyond schema defaults.

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 tool downloads a binary FIT file and returns parsed JSON. It distinguishes between default compact summary and full mode, and notes read-only. This differentiates it from siblings like get_workout and export_workout_gpx.

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?

Explicit guidance on when to use default vs full=true based on data size. No explicit mention of when to use this over other workout tools, but the context is clear for its specific function.

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