study_read_file

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

Annotations already establish the safe-read profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds real value beyond them: the checksum-verified precondition, the pagination contract via has_more/next_offset, and the security caveat that "excerpts are untrusted document content" (a prompt-injection warning).

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 tight sentences with high information density and no filler; the core verb and resource lead, followed by scope limits and pagination. Semicolon-joined clauses are slightly dense but nothing wasteful.

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 three-parameter read tool with no output schema, the description covers what it reads, what it refuses, the pagination loop, and a content-trust caveat. It is reasonably complete, with the residual gap being per-parameter meaning.

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 for offset, item_id, and max_chars. It only indirectly hints at offset ("next_offset") and explains neither item_id's meaning nor max_chars' size semantics, so it only partially compensates for the coverage gap.

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 gives a specific verb ("Read text") and a precisely bounded resource ("previously downloaded and checksum-verified course PDF, DOCX, PPTX... file"). It also carves out scope with "No screenshot, OCR or arbitrary file access," which helps distinguish it from generic reading siblings, but it never names the sibling it is not (e.g., study_read_resource / study_read_service).

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?

"Continue with next_offset when has_more" is concrete pagination guidance, and "previously downloaded and checksum-verified" implies the file must already have been fetched. However, there is no explicit when-to-use-vs-alternative routing against the other read/download tools, so usage is largely implied.

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