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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the bar is lower, and the description still adds genuinely useful behavior context: it performs no UI action itself ('opens nothing by itself') and the official TrainingPeaks API is unavailable to personal users, explaining why browser automation is required. It does not describe the shape or length of the returned guidance.

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 instruction is front-loaded and actionable, but filler such as 'from ChatGPT, Claude or any AI agent' consumes space without informing the call, and the API-availability aside, while relevant, could be compressed to a clause. The valuable sequencing advice is buried mid-sentence after the misleading opening.

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 responsibility for explaining what comes back, and it does: step-by-step screens, buttons and fields. What it omits is that the result is generic guidance rather than data about one specific workout, which matters for how the agent chains into the browser tools.

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 to disambiguate and the baseline of 4 applies. The description could usefully have confirmed that the guide is generic and the specific workout is selected later in the browser, but no parameter confusion arises.

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 opening sentence claims it will 'Get workout details,' but the second sentence reveals it actually returns step-by-step instructions (screens, buttons, fields) and 'opens nothing by itself.' Once read in full the purpose is understandable, but the leading framing points at a different action than the tool performs, which is a real risk given the tool 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?

The description gives a clear workflow: call this first to obtain the click-by-click steps, then carry them out with cotlet_browser_* tools in the user's TrainingPeaks Cloud Browser. It does not explicitly contrast with cotlet_app_guide or explain what to do if the returned steps don't match the UI, but the when-to-use sequencing is unambiguous.

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