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

Annotations declare readOnlyHint/idempotentHint true and destructiveHint false; the description reinforces this with the non-obvious detail that it opens nothing and only returns instructions, which is the key behavioral fact an agent could otherwise get wrong. It also describes the shape of the return (screens, buttons, fields), though it doesn't cover output format or failure modes.

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 facts are front-loaded, but the trailing sentence about Lichess's official REST API and 'no official MCP server (checked 17 Oct 2026)' is context that doesn't help an agent invoke this specific tool, and the dated parenthetical is noise.

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 it returns and what to do next, which is the information an agent actually lacks. The only omission is any indication of how the instructions are structured beyond 'step by step'.

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 closed, so there is nothing to disambiguate; the description correctly implies no inputs are needed. Baseline for 0 params applies.

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 first sentence names a specific verb, resource and scope ('Accept team join request in the user's own Lichess account'), then immediately corrects the impression the name creates by stating it returns step-by-step UI instructions and 'opens nothing by itself'. An agent can tell this is an instructional generator rather than an executing action, though the mismatch with the tool name adds a moment of ambiguity.

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 concrete workflow: read the returned steps, then perform them with the cotlet_browser_* tools in the user's Lichess Cloud Browser. That is clear next-step guidance and rules out treating this tool as the actor, but it never states when to choose this over the Lichess REST API it mentions, nor any exclusions.

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