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

Annotations already declare readOnlyHint and openWorldHint, so the safety and reach profile is covered. The description adds one genuinely new behavioral fact — player identity headers are omitted — but leaves 'source-random' unexplained and says nothing about rate limits or failure behavior for an open-world fetch.

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 tight sentences with the payload and the privacy caveat front-loaded before the usage hint. The second sentence partially restates the first's privacy point, and 'source-random' is an unexpanded term that costs a little clarity.

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 parameterless read with an output schema present, the description supplies the essentials: what comes back and the identity-header caveat, so return-value detail need not be repeated. The residual gap is how this differs from the non-random sibling puzzle tool.

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, so there is nothing for the description to disambiguate; the baseline applies. No misleading parameter hints are introduced.

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 and resource ('Returns a ... Chess.com puzzle') and enumerates the payload (FEN, source link, PGN moves), which is far beyond a tautology. It does not, however, distinguish itself from the sibling chesscom_puzzle, so an agent must infer what makes this one different beyond the word 'random'.

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?

'Use this to fetch a random tactic without player-profile data' gives a positive use case and an implicit exclusion (player-profile lookups). It never names an alternative tool or states when not to call it, so routing between this and chesscom_puzzle is left to inference.

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