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

Goes well beyond the annotations by disclosing that nothing is fetched at invocation time and that Chess.com/Lichess is read only when the user opens the link, plus that Stockfish runs client-side. These are non-obvious deferred-side-effect semantics the readOnlyHint/idempotentHint annotations cannot express. It omits failure behavior for invalid or non-public links.

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?

Three sentences, zero waste: the core transformation is front-loaded, then the deferred-fetch behavior, then the unsupported-case caveat. Every sentence earns its place and none repeats schema or annotation content.

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 one-parameter, read-only link-generator with an output schema covering the return, the description supplies everything an agent needs: accepted inputs, unsupported inputs, when external fetching happens, and where the review is computed.

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?

Schema coverage is 100% and the single url parameter is already documented in the schema. The description's only added semantic is the daily-game exclusion and the public/live constraint, which is modest incremental value over the structured field, so the baseline 3 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?

States a specific verb+resource+output: converts a public Chess.com live or Lichess game link into a chessigma.com review link. The transformation target and the computing engine (Stockfish in the browser) are explicit, so an agent can distinguish it from PGN-based siblings like analyze_game.

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?

Clearly scopes usage to public live/correspondence-supported game links and explicitly excludes Chess.com daily games, redirecting to 'ask for the PGN instead'. It stops short of naming the sibling tool (e.g. analyze_game) that should handle that PGN path, so the routing is implied rather than spelled out.

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