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

Annotations already declare readOnlyHint and openWorldHint; the description still adds real value by disclosing server endpoints, null cases (pot null if not read; BlockRolls null means practice/free rolls with nothing to sign) and the effect of supplying `wallet`. It stops short of describing response shape or freshness/caching behavior, so it is good but not rich.

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 entire definition is a single sprawling sentence with deeply nested parentheticals, making it hard to parse and locate a given field. The content is largely load-bearing (it substitutes for a missing output schema), but it is not front-loaded or structured for scanning.

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 correctly carries the burden of enumerating return sections and their null semantics, which is the right call for a multi-part read tool. It is close to complete, though the enumeration's density makes some fields easy to miss on a first read.

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 schema description is thin ('wallet whose ticket and progress to read'), so the description genuinely extends it: adding `wallet` yields that wallet's held/not-held status, verified volume, skin pass, its 5-trait ticket face, and this week's entries. This is information the schema alone does not convey.

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?

Specific verb and resource ('Reads the Game tab ... GET /api/tirage') with an enumeration of the exact payload sections (tickets, pot, preview face, BlockRolls, practice rolls). It does not explicitly contrast with siblings like tblock_panel_state, so an agent must infer the division of labor, but the purpose itself is unambiguous.

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?

No statement of when to call this versus siblings; the only routing hint is incidental ('the 5-trait guess tblock_plan_roll uses by default'), which explains lineage rather than when to pick this tool. 'Read-only' is a property, not usage guidance.

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