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

Beyond the readOnly and idempotent annotations, the description discloses important behaviors: it reads only bounded pages, returns actual page images, does not transcribe image-only pages, and never starts processing. This gives an agent a realistic model of what to expect and what limitations exist.

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?

Two concise sentences with no filler. The key behavior, output contents, limitation, and fallback guidance are all packed efficiently, with the core action front-loaded.

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?

The description is largely complete given the output schema and annotations: it covers scope, safety, page boundaries, image behavior, and a fallback path. The only notable gap is parameter acquisition — specifically how to know the cheatsheetId — but list_cheatsheets likely covers that elsewhere.

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%, so the description carries the burden of parameter meaning, but it does not explain cheatsheetId, page, or limit explicitly. 'Bounded pages' hints at the page and limit parameters, but the agent is left to infer how they work and how to obtain cheatsheetId.

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 clearly states a specific verb ('Read') and resource ('official Fiveable PDF' cheatsheet), and adds what the result includes: page citations, extracted text, and images. It distinguishes this read-based tool from listing or scoring siblings by emphasizing 'bounded pages' and 'prepared official' 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?

The description gives explicit guidance for the fallback case ('If artifacts are unavailable, use the approved PDF link') and notes that this tool never starts processing, signaling a safe read. It does not explicitly name sibling tools or state when to prefer this over list_cheatsheets or get_study_guide, but the intended context is reasonably clear.

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