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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is covered. The description adds genuinely useful context beyond them: it returns step-by-step screens/buttons/fields instructions and performs no action itself, and it explains the browser-tool handoff. However, it never describes what the returned guidance actually looks like or whether it depends on any user context.

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 critical facts (returns steps, opens nothing, use cotlet_browser_* next) are front-loaded in the first two sentences. The closing sentence about Lichess's official REST API and the absence of an official MCP server is tangential justification rather than actionable guidance, and it dilutes an otherwise tight definition.

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, the description covers what matters: it produces procedural guidance rather than performing the creation, and it names the tools that carry out the actual work. The main residual gap is that it never states whether the guide is generic or tailored, given that no tournament name or settings can be passed in.

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 and the schema is empty with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies. The description could have noted that the returned steps are generic because no tournament settings are accepted, but that is a minor omission.

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?

Names a specific resource (Arena tournament) and immediately corrects the imperative-sounding name by stating it 'Returns how to do it in Lichess step by step ... and opens nothing by itself'. An agent can tell this is a guide-producing tool rather than an action tool. It does not explicitly differentiate itself from sibling tools like lichess_create_broadcast, but the purpose is unambiguous.

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?

Explicitly routes the agent to the follow-up workflow: 'then do it with the cotlet_browser_* tools in the user's Lichess Cloud Browser'. That is clear when-to-use guidance for the downstream step. It lacks exclusions (when not to use this) and prerequisites such as whether the user must already be logged into Lichess.

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