tp_analyze_workout

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

The description discloses the side effect of saving a full time-series to a JSON file, which is a behavioral trait beyond a simple query. However, it does not mention other important aspects like authorization requirements, file storage behavior, or potential performance implications.

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 sentences, no superfluous words. The first sentence states the main purpose, and the second adds a key behavioral detail. Efficient and front-loaded.

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?

Given the lack of output schema, the description should clarify what the tool returns (structure of metrics, zones, laps). It mentions saving to JSON but not the response format. Contextually adequate for a data-retrieval tool but missing output details.

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?

The input schema has two parameters but only athlete has a description. The tool description does not add any additional meaning to the parameters, leaving workout_id unexplained. With 50% schema description coverage, the description fails to compensate for the lack of detail.

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 returns workout analysis including metrics, zones, and laps, and uniquely mentions saving time-series data to a JSON file. This distinguishes it from sibling tools that deal with workout creation, deletion, or comments.

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 guidance is provided on when to use this tool versus alternatives, such as tp_get_fitness or tp_get_workout_comments. The description does not specify prerequisites or typical use cases.

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