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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false and destructiveHint=false, so safety matters are covered. The description adds real behavior beyond that: it runs in the user's actual signed-in Chrome, it reuses the site's existing tab rather than spawning one, and it returns the page's elements/text 'with the same numbers'. It does not mention auth failures or timeouts, but the added context is substantive.

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 core action and the 'Call it first' instruction, both high-value. The TrainingPeaks action list is long and partly restates sibling tool names, which costs some length, but it grounds the tool in a concrete use case. Overall tight and well-ordered.

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?

No output schema exists, so the description correctly compensates by describing what comes back ('the elements and text in view, with the same numbers'). For a 2-param browser entry tool with no required params and strong annotations, this is nearly complete; only error/failure behavior is unaddressed.

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?

Schema coverage is 100%, so the schema already documents both `url` and `app`. The description still adds value by explaining `app`'s real semantics in prose (default is the user's browser; only set when cotlet_app_guide names an app's own Cloud Browser), which is the exact decision point the agent must reason about. Slightly redundant with the schema text, so not a 5.

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 specific verb and resource ('Starts the user's Cloud Browser... and opens `url`'), and distinguishes it from siblings like cotlet_browser_navigate by tying it to the user's real, signed-in Chrome session and the shared tab behavior. An agent can see this is the entry point rather than a navigation or read tool.

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?

Explicit sequencing guidance: 'Call it first' and 'Answers the page after it' tell the agent this must precede interaction tools. The URL routing rule (site's open tab, else new tab) and the preserved-tabs constraint give clear when-to-use context. It also enumerates the TrainingPeaks actions it serves, linking to the sibling tools' domain.

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