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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety bar is lower. The description still adds the crucial behavioral fact not captured there: the call performs no action against Strava and instead returns a UI walkthrough (screens, buttons, fields) to be executed later. The trailing remark about Strava's official API and MCP connector is irrelevant trivia but does not obscure the behavior.

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 two operative sentences are dense but reasonably front-loaded, though the mechanism disclosure lands mid-sentence rather than first. The final sentence about Strava's official API and connector (with 'checked 27 Oct 2026') is irrelevant metadata for an agent deciding how to call the tool and should be dropped.

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 must explain what comes back, and it does at a high level (a step-by-step guide with screens, buttons, fields). What is missing is how the returned steps map to the cotlet_browser_* tools and what the response looks like structurally, which matters for a tool whose entire output is guidance text.

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 for the description to disambiguate and the schema carries no burden. The baseline of 4 applies, and nothing in the text misrepresents the parameterless call.

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 clause says it will 'List activities in the user's own Strava account', but the next clause reveals it only returns step-by-step instructions and 'opens nothing by itself'. The real function (a how-to guide for a Strava activity list, executed via cotlet_browser_* tools) is stated, but only after a misleading lead that duplicates the title, so an agent skimming could believe this tool performs the listing.

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 does give a follow-on path: read the steps, then act with the cotlet_browser_* tools in the user's Strava Cloud Browser. It offers no explicit when-not-to-use guidance and does not distinguish itself from the closely related cotlet_app_guide or cotlet_apps siblings, leaving the agent to infer which guide tool to pick.

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