tp_update_speed_zones

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'Update' without revealing whether it replaces all pace zones, performs partial updates when one parameter is omitted, or requires any special permissions. No side effects, reversibility, or safety information is provided.

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 a single, front-loaded sentence with no redundant wording. It conveys the essential purpose in a compact form, and every word earns its place. This is appropriately concise for the level of detail provided.

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 that this is a mutation tool with no annotations, no output schema, and 3 optional parameters, the description is too sparse. It does not explain what happens when all parameters are omitted, whether it updates only the provided zone types, or what the return value is. Key behavioral context is missing.

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 provides complete parameter descriptions, including examples (e.g., '4:30/km') and the athlete parameter's coach-account restriction. The tool description itself adds no parameter-level meaning, so it does not exceed the schema baseline. At 100% schema coverage, the description need not compensate.

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 clear action and resource: 'Update run/swim pace zones.' This distinguishes it from sibling tools like tp_update_hr_zones (heart rate zones) and tp_update_ftp (functional threshold power). It could be more precise by mentioning 'threshold pace' explicitly, but the schema parameters (run_threshold_pace, swim_threshold_pace) clarify the scope.

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 given about when to use this tool versus alternatives. It does not mention that this tool is specifically for pace zones while other sibling tools handle different metrics, nor does it explain any prerequisites such as coach accounts for the athlete parameter (which is only in the schema). There is no explicit 'when to use' or 'when not to use' context.

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