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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantive context beyond them — which fields are omitted (player records, game cross-references, PGN identity headers) and that rate-limit cost scales with the number of IDs. That cost model and field-omission note are exactly the kind of disclosure annotations cannot carry.

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?

Two dense sentences with zero filler: the primary action and limits come first, followed by the omission and cost caveats. Every clause carries distinct information an agent needs.

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 batch read with an output schema available, the definition covers scope, omissions, and the rate-limit cost model, which is most of what matters. It stops short of describing behavior for invalid or partially-valid ID lists, which would matter for a 50-item batch.

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 'ids' parameter already documents the comma-separated 1–50 format. The description restates the same constraint rather than adding syntax, error behavior, or partial-failure semantics, so it meets the baseline but does not exceed it.

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 ('fetches') and resource ('public Lichess puzzles') with explicit batch scope ('1–50 ... by their comma-separated IDs'). The phrase 'in one source request' signals the batching benefit that separates it from single-puzzle retrieval, though no sibling is named outright.

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?

Implies batch usage by noting the 1–50 range and that the source charges rate-limit cost per ID, which nudges an agent toward batching rather than looping. However, it never explicitly says when to prefer this over lichess_puzzle or lichess_puzzle_batch, leaving the choice to inference.

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