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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description still adds value beyond them: it explicitly says it 'opens nothing by itself' (no side effects despite being about a browser session) and explains why the browser route is necessary — TrainingPeaks' API is partner-only and unavailable for personal use. That is exactly the kind of context annotations cannot carry.

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?

Front-loads the most decision-relevant fact (it returns steps, it opens nothing) and then the follow-up tool family. The opening clause 'from ChatGPT, Claude or any AI agent' is filler, and the dated API note is slightly tangential, but both are short and the latter justifies the browser-based approach.

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 no-parameter, no-output-schema guide tool, an agent has everything needed: what it returns, that it is side-effect free, and which tool family to use next. Nothing essential is missing; only explicit contrast with a sibling guide tool would 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No misleading parameter-like claims are made.

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 resource (fitness, fatigue and form) and immediately corrects the likely misreading by saying it 'Returns how to do it in TrainingPeaks step by step (screens, buttons, fields) and opens nothing by itself.' That makes the tool's real nature — an instructions provider, not a data fetcher — unambiguous. It stops short of naming a specific sibling (e.g. cotlet_app_guide) as the alternative, so differentiation is by behavior rather than by name.

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 operating sequence: call this first to learn the steps, 'then do it with the cotlet_browser_* tools in the user's TrainingPeaks Cloud Browser.' That is real when-to-use guidance tied to the follow-up action. It does not state when NOT to use it or how it differs from other guide-type siblings, so it is not a full 5.

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