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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the closing 'Read-only' merely restates that. The description does add real context the annotations cannot: the data sources (federation, watch, scanned cards over the last year), the WHS derivation, and the confidence value returned. It is a modest but genuine contribution beyond the structured fields.

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 short sentences that are front-loaded with the definition, then the audience, then the output constraint. The only wasted words are the trailing 'Read-only,' which duplicates the annotations, but everything else earns its place.

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 parameters and no output schema, the description carries the burden of describing the return value, which it does (handicap estimate plus confidence) along with provenance. The remaining gap is vertical differentiation from the four other handicap-estimation siblings, which are left unmentioned in a very crowded toolset.

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. Baseline for an empty schema is 4; no parameter-level gaps exist.

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 ('Estimate the player's real playing level') and defines the output precisely: a WHS-formula handicap computed from the last year's cards plus a confidence value. It implicitly contrasts with the official handicap, but never names the closely related siblings (plays_like, project_handicap, simulate_handicap, get_handicap) so an agent cannot separate it from those without reading each one.

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?

Gives a clear triggering condition: 'For a player who says their official handicap does not reflect how they play,' plus a presentation rule ('Always present it as an estimate next to the official one'). No explicit when-not case or named alternative such as get_handicap for the official figure, which keeps it from a 5.

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