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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower. The description adds real behavior beyond them: image-only pages are never guessed at, unavailable artifacts fall back to the approved PDF link, and the read never triggers processing. Return format specifics are left to the output schema.

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 tightly packed sentences with no filler, front-loading what the tool does and following with fallback behavior. Slightly dense but every sentence 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?

An output schema exists, so return values needn't be re-explained, and the safety profile comes from annotations. What is missing is prerequisite context (where cheatsheetId comes from) and any parameter guidance for a 0%-coverage schema, leaving the definition adequate but not complete.

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 description coverage is 0% and three parameters are required, so the description must carry the load. 'Bounded pages' gestures at page/limit semantics but never explains the cheatsheetId format (cs_ + 24 hex chars), the 1-32 page range, the 1-3 limit cap, or why limits exist. The schema alone leaves an agent guessing.

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 ('Reads bounded pages from a prepared official Fiveable PDF') and specifies the distinctive output (page citations, extracted text, page images). It is clearly distinguishable from the sibling list_cheatsheets, which enumerates rather than reads content.

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?

Usage is implied by the name and the pixel-level output described, but the description never says when to prefer this tool over siblings like get_study_guide or get_guided_notes, nor does it state that a cheatsheetId must first come from list_cheatsheets. Adequate but with a clear routing gap.

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