tp_get_athlete_settings

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

With no annotations provided, the description must carry the burden of behavioral disclosure. It lists the data returned (FTP, thresholds, zones, profile), which is useful, but it does not explicitly state that the operation is read-only, mention permissions beyond the schema's coach note, or explain potential errors or side effects.

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, well-front-loaded sentence that efficiently communicates the tool's purpose and scope. No unnecessary words or repetition, making it an ideal concise description.

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 simple getter with one optional parameter and no output schema, the description is adequately complete: it names the resource and the primary data categories returned. It could mention whether the response reflects current or saved settings, but overall it provides enough context for correct tool 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?

The schema provides 100% coverage for the single optional parameter, clearly describing it as a target athlete name/ID for coach accounts. The description adds no additional parameter semantics, so the baseline of 3 applies.

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 gets 'athlete settings' and enumerates specific contents (FTP, thresholds, zones, profile), which distinguishes it from sibling tools like tp_get_profile. It uses a specific verb 'get' and a clear resource, though it could more explicitly differentiate itself from closely related getters.

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 tool's usage is implied by its name and description as a getter for athlete settings, and the input schema notes the optional athlete parameter is for coach accounts only. However, there is no explicit guidance on when to use this tool versus alternatives like tp_get_profile or tp_get_fitness, and no exclusions are stated.

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