read_content

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds real context beyond them: pagination via next_offset, links returned for formats without text extraction, and an explicit non-scope statement ('doesn't send tasks or publish messages'). It stops short of saying what a page/truncation boundary looks like in practice.

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?

Very short and front-loaded: the core capability is in the first clause, followed by pagination and return-format notes. Minor waste in the trailing scope sentence, but nothing bloated.

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 simple read-only tool with no output schema, it covers return behavior (extracted text vs. links) and pagination reasonably. The gaps are the undocumented offset/max_chars inputs and the absence of any indication of what the response looks like beyond 'next_offset'.

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 full burden. It references pagination ('next_offset') and thus hints at the offset param, but the name doesn't match the actual 'offset' parameter and max_chars (the 30000-char truncation knob) is never explained anywhere.

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?

Names a specific verb (read) and enumerates the resource types it handles: activity, folder, page, book chapter, PDF from the classroom. That scope implicitly separates it from list_courses/get_course_contents/search_course_contents, but no sibling is ever named, so an agent must infer the boundary.

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 genuine usage hint for recursion: folders and books return links that can be read with this same tool. However, it never states when to pick this over search_course_contents or get_course_contents, nor what input (URL) is expected to come from those tools. Usage is implied rather than prescribed.

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