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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds real context beyond that: it opens nothing by itself, it hands back a procedure rather than data, and the actual interaction happens through separate browser tools. The 'official API: Yes (checked 6 Nov 2026)' sentence adds nothing operational.

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 is front-loaded in the first sentence and a half, which is good. However, 'from ChatGPT, Claude or any AI agent' and the dated API-availability aside are filler that dilute an already short description and push the useful 'opens nothing by itself' clause into the middle.

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?

The tool is simple (no params, no output schema) and the description covers what it returns and that it has no side effects. What is missing is orientation within the wider Intervals.icu toolset: no mention of when guidance is needed versus when a direct data call (list_activities, get_power_curve) is the right choice, which matters for an agent picking among many siblings.

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 schema is fully self-describing. The description correctly implies no inputs are needed by describing the call as a context-free lookup of guidance for the user's own account.

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 concretely what the tool returns: step-by-step instructions (screens, buttons, fields) for getting an activity with intervals in the user's own Intervals.icu account. That is more specific than the name, which reads like a data-retrieval call. There is some residual tension between the name and the guidance-returning behavior, but an agent reading the description can tell what it will get back.

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 names the follow-up path explicitly: use the cotlet_browser_* tools in the user's Intervals.icu Cloud Browser after this returns. But it never says when to prefer this over data-returning siblings like intervals_icu_list_activities or over the generic cotlet_app_guide, so an agent still has to guess which entry point fits.

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