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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds that this is the *whole* manual versus a condensed cheat sheet. It does not disclose size, format, or token cost of retrieving an entire manual, which is the main behavioral risk for a no-parameter reference tool.

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?

A single short sentence with no filler. The phrasing 'for what ... leaves out' is slightly elliptical and requires a second parse, which costs it the top score.

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 zero-parameter reference tool with annotations covering safety and no output schema, the description conveys the essential fact — you get the entire manual. The one meaningful omission is any hint about output shape or volume, but nothing needed to invoke it correctly is missing.

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 of 4 applies. The description correctly implies a single unfiltered retrieval with no scoping options.

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?

Identifies the resource precisely — the complete manual for the Worksheet script language — and distinguishes it from the sibling solve_worksheet's 'cheat sheet'. The verb is implicit ('The ... whole manual') rather than an explicit 'returns/gives', which keeps it just short of a 5.

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?

'For what solve_worksheet's cheat sheet leaves out' names the alternative and implies the ordering: consult the cheat sheet first, come here only for gaps. It gives no explicit exclusions or guidance on how much of the manual to expect, so it stops short of a 5.

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