lichess_daily_puzzle

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

Annotations already declare readOnly, openWorld, and idempotent. The description adds the auth requirement ('Auth: none needed') and explicitly lays out the return structure, which goes beyond structured data. It doesn't mention timezone or reset behavior, but that's minor given the safety profile is covered.

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 description is brief and well-structured with a summary, return format, example, and auth line. The 'Example' field is vague but not harmful. It earns its place without unnecessary verbosity.

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?

With no output schema, the description compensates by listing all return fields under 'Returns:' with types and examples. It could clarify some field semantics (e.g., initialPly) but is largely complete for a parameterless daily puzzle fetcher.

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 has zero parameters, so schema coverage is trivially 100%. Per guidelines, baseline for 0 params is 4; the description doesn't need to add parameter information.

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 description identifies the resource as the daily puzzle and lists its components (position, solution line, source game), and the 'Returns' section clarifies it's a retrieval operation. However, it lacks a direct verb like 'Get' and does not explicitly distinguish itself from other chess tools, though it's the only daily puzzle tool.

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?

The description implies usage when the daily puzzle is needed, and the example 'Today's puzzle' suggests a simple call. However, there is no explicit guidance on when to use this vs. other Lichess tools, no exclusions, and no mention of daily update timing.

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