get_logged_in_athlete_zones

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states 'Read-only operation' and requires the scope 'profile:read_all', which are important for an agent to know before invoking. It does not cover rate limits or error behavior, but for a simple read-only GET, this is sufficient. The description adds meaningful behavioral context beyond the schema.

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 begins with 'Get Zones', which merely restates the tool name and adds little value. It then repeats the scope requirement twice ('Requires profile:read_all' and 'Scopes: required: profile:read_all'). While the information is accurate, the structure is not tightly front-loaded and includes redundancy. It is verbose for such a simple operation, but not excessively long.

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?

For a parameterless GET with no output schema, the description covers the key facts: what is returned (heart rate and power zones for the authenticated athlete), the scopes needed, and the read-only nature. There is no missing information that an agent would need to decide whether and how to call this tool. It is complete for its simplicity, though a brief note on output format would slightly improve it.

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?

There are zero parameters, so the schema fully covers them (100% coverage). The baseline for 0 parameters is 4, and the description does not need to add parameter details. It correctly omits any parameter-based explanation, so no deduction is warranted.

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 identifies the resource as the authenticated athlete's heart rate and power zones. The name itself is specific enough to distinguish from sibling get_zones_by_activity_id, and the description reinforces that it is for the logged-in athlete. However, it does not explicitly contrast with activity-specific zones, which would make differentiation more explicit.

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 gives no guidance on when to use this tool versus alternatives. It does not mention get_zones_by_activity_id or any condition that would select one over the other. An agent is left to infer usage purely from the name and endpoint, which is inadequate for clear routing.

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