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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely new behavioral facts: it opens nothing by itself and returns screens/buttons/fields as text, which tells the agent not to expect data back or any side effect.

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 is stated early, which is good, but the opening clause ('from ChatGPT, Claude or any AI agent') is marketing filler and the closing note about Strava's official API/MCP connector is presented without any actionable instruction, so it does not earn its place.

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?

For a zero-parameter guidance tool with rich annotations and no output schema, most of what an agent needs is present: no side effects, what is returned, and which tools to chain next. It omits prerequisites such as whether the user must already be signed in to Strava and how the target club is determined.

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 no schema semantics to explain and the baseline is 4. The description does not need to compensate for anything here, though it also never explains which club's leaderboard applies given no club argument exists.

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 verb and resource (read club leaderboard) and then clarifies the actual mechanic: it returns step-by-step Strava instructions rather than the leaderboard data itself. That correction is valuable, but it is not differentiated from the sibling cotlet_app_guide, which plausibly does the same kind of thing.

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 usable sequence: get the guide here, then execute it with cotlet_browser_* tools in the user's Strava Cloud Browser. It does not say when to prefer this over cotlet_app_guide, nor what the agent should do with the official API/MCP connector fact it raises, leaving the alternative path ambiguous.

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