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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false; the description earns credit for explicitly confirming 'opens nothing by itself' and describing the return content (step-by-step screens/buttons/fields). It also explains the constraint that drives the design — TrainingPeaks' API is restricted to approved commercial partners, hence the browser-tool handoff — which is context the agent cannot get from annotations.

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 behavior and the browser-tool handoff are front-loaded and clear, but 'from ChatGPT, Claude or any AI agent' is filler that adds no selection value. The closing API-availability sentence is genuinely useful context but is wordy enough (including a dated check) that the description runs longer than its two actionable facts require.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does — step-by-step instructions naming screens, buttons and fields. It also explains the required follow-up tool family, so an agent knows the task is not complete after this call. Only the lack of differentiation against sibling add/plan tools keeps it short of a 5.

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 and the schema is empty, so the baseline of 4 applies. The description correctly implies the target account is scoped by the user's own TrainingPeaks session rather than by an argument, which matches the empty schema and avoids the agent hunting for a missing parameter.

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 and output: it returns step-by-step instructions (screens, buttons, fields) for adding a workout from the library in the user's own TrainingPeaks account. Crucially it clarifies that this is an instructional tool that 'opens nothing by itself', which resolves the write-sounding name. It does not, however, distinguish itself from sibling trainingpeaks_add_planned_workout, so an agent cannot tell which add-path to pick from the description alone.

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 a clear follow-on workflow — 'then do it with the cotlet_browser_* tools in the user's TrainingPeaks Cloud Browser' — which tells the agent this is step one of a two-phase process. What is missing is any explicit condition for choosing this over the other add/plan tools (trainingpeaks_add_planned_workout, trainingpeaks_apply_training_plan). Usage is implied by the tool's subject rather than stated as when/when-not.

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