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

Adds real behavioral context beyond the annotations by stating it 'opens nothing by itself' and returns procedural guidance, which prevents an agent from assuming a side effect occurred. Annotations already declare readOnly/idempotent/non-destructive/closed-world and the description stays consistent with them. It does not describe the shape or length of the returned steps, which would help chaining.

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?

Purpose and the critical 'opens nothing by itself' caveat are front-loaded, which is good. But the trailing 'TrainingPeaks's official API: TrainingPeaks has an API, but only approved commercial partners get it...' is repetitively worded, and the 'from ChatGPT, Claude or any AI agent' clause adds no decision-relevant information.

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 zero-parameter, no-output-schema tool this covers what an agent needs: what it returns, that it has no side effects, and which tool family to use next. The only gap is the granularity of the returned instructions, which matters for deciding whether one call is enough before switching to cotlet_browser_*.

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 tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the schema shows. Baseline for a parameterless tool applies; it correctly makes no parameter claims.

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?

States a specific verb and resource ('List athletes in the user's own TrainingPeaks account') and then explicitly redefines what the tool actually returns: step-by-step screens/buttons/fields guidance rather than data. That redefinition is important because the tool name alone would mislead, but the description never positions it against the trainingpeaks_* data siblings, so an agent must infer the split.

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?

Gives a clear sequencing rule: call this to get instructions, 'then do it with the cotlet_browser_* tools in the user's TrainingPeaks Cloud Browser.' It also justifies why the browser route exists (the official API is commercial-partner-only), removing the obvious 'why not just use the API' doubt. It stops short of naming when NOT to use it, e.g. when another trainingpeaks_* tool already covers the need.

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