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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered structurally. The description adds genuinely useful behavior beyond that: the return value is a human-readable walkthrough of screens, buttons, and fields, and the call itself never touches the account. The note on TrainingPeaks' API being partner-only explains why the browser fallback exists.

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 core mechanic and the browser hand-off are front-loaded, which is good. But the opening 'from ChatGPT, Claude or any AI agent' is marketing filler, and the closing paragraph about TrainingPeaks' API licensing is background context that occupies roughly a third of the text without changing how the tool is called.

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 output schema and no parameters, the description does most of the work by explaining that the output is a step-by-step guide, which is adequate for correct invocation. It stops short of what an agent most needs to know: since no workout can be specified, are the returned steps generic instructions, or does the tool resolve a workout from conversation context? That gap matters for a tool whose name implies a specific target.

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?

Zero parameters, so the baseline is 4 per the scoring rules. One residual ambiguity is unaddressed: the description never explains that no workout identifier is accepted, so an agent might expect to pass a workout ID and be surprised by the empty schema — but nothing in the schema is left undocumented.

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 states a concrete verb+resource (move a workout in the user's TrainingPeaks account) and then clarifies the actual mechanic: it returns step-by-step instructions rather than performing the move. That distinction from siblings like trainingpeaks_add_planned_workout is implicitly drawn by the 'opens nothing by itself' clause, though it never explicitly contrasts itself with the other trainingpeaks_* tools.

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 says what to do after calling: perform the described steps with the cotlet_browser_* tools in the user's Cloud Browser, which is the key routing instruction. It gives no explicit exclusions (e.g., don't use this if the workout is in a plan you can edit via API), but the when-to-use context is clear enough to act on.

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