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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered; the description reinforces this with 'opens nothing by itself' and describes the return payload ('step by step (screens, buttons, fields)'). The closing sentence about Lichess's official REST API and OAuth tokens is tangential and adds no behavioral value for invoking this tool.

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 mechanics are front-loaded in the first sentence, which is good. However, the trailing sentence about Lichess's official API, personal/OAuth tokens, and 'checked 17 Oct 2026' is filler that does not help an agent select or invoke the tool.

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, no-output-schema tool it covers the essentials: what it returns and which tools complete the task. The key gap is that it never says how the broadcast parameters are supplied given the empty input schema, nor what account/session prerequisites must hold before the browser handoff.

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 no parameters, so the baseline is 4. Nothing in the description contradicts the empty schema, though it also never explains how the broadcast specifics (name, rounds, time control) are conveyed to the tool — presumably from conversation context, which goes unstated.

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 ('Create broadcast in the user's own Lichess account') and immediately clarifies the actual mechanism: it returns step-by-step instructions and 'opens nothing by itself.' The dual framing (imperative name vs. advisory behavior) is slightly confusing, but the net effect is that an agent can distinguish this from sibling tools like lichess_create_arena_tournament.

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 explicitly tells the agent what to do after calling: 'then do it with the cotlet_browser_* tools in the user's Lichess Cloud Browser,' which is a concrete usage path. It does not state when NOT to use it (e.g., if the user has no Lichess Cloud Browser session), leaving one exclusion unstated.

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