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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description earns credit by resolving the tension between the name 'apply' and read-only behavior: 'opens nothing by itself.' It also discloses the return content (screens, buttons, fields) and explains the API constraint that forces the browser route, which no annotation conveys.

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 operative facts are grouped sensibly: what it returns, that it performs no action, and which tools to use next. Minor waste exists in the audience list ('from ChatGPT, Claude or any AI agent') and the dated API aside, which is rationale rather than instruction but is at least kept to the end.

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?

With no input parameters and no output schema, the description carries the full burden of explaining what comes back, and it does so concretely (step-by-step screens, buttons, fields). It also preempts the obvious agent question — 'can I call the TrainingPeaks API instead?' — with a definitive answer.

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 and the baseline of 4 applies. It neither helps nor harms parameter understanding.

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 names a specific resource (training plan) and, critically, redefines the verb: what the tool actually produces is step-by-step guidance (screens, buttons, fields), not the applied plan. That distinction separates it from the sibling mutation tools like trainingpeaks_add_planned_workout that actually perform writes.

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?

It gives an explicit handoff: call this to get the procedure, then execute it with the cotlet_browser_* tools in the TrainingPeaks Cloud Browser, which is named directly. The only gap is the absence of an exclusion case — it never says when not to call this (e.g., a plan already active or no plan selected).

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