tp_update_hr_zones

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

With no annotations, the description bears the full burden for behavioral disclosure. It only says 'Update heart rate zones,' offering nothing about side effects, permission requirements, reversibility, or what happens to existing zones. This is even sparser than the mid-tier example, which at least listed affected fields.

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 extremely brief (four words), which might seem concise, but it is under-specified rather than appropriately concise. For a tool with five parameters and no annotations, the description should convey more than just the operation.

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 complexity of five optional parameters, no output schema, no annotations, and only a 20% schema coverage, the description is wholly inadequate. It fails to explain what heart rate zones are, how the parameters interact, or what the update impacts, making it nearly useless for correct 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 description coverage is only 20% (just the 'athlete' parameter has a description). The tool description mentions none of the parameters, leaving max_hr, resting_hr, threshold_hr, and workout_type undefined. The agent cannot infer their meaning, units, or constraints from the description.

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 verb ('Update') and the resource ('heart rate zones'), making the tool's primary action obvious. However, it does not distinguish itself from sibling tools like tp_update_speed_zones or tp_update_ftp beyond the zone type, and it lacks any scope detail.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of the 'athlete' parameter for coach accounts. There is no context about typical use cases or exclusions, leaving the agent to infer when this update operation is appropriate.

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