Get Announcement Files

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

No annotations exist, so the description carries the burden, and it does much of that: it discloses the dual behavior (listing vs reading), that the response is the extracted text itself, and that a sibling should be used for on-disk saving. It omits prerequisites/permissions and rate considerations, so it stops short of full transparency.

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?

The usage rule and the two-step protocol are front-loaded, and every sentence contributes new information (what it reads, how to call it, when to use it, what it returns, when to use the alternative). No filler.

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 read tool with no output schema and no annotations, the description covers the return value ('Returns the text itself'), the listing behavior, and the sibling routing. Only minor gaps remain, such as permissions or what the listing mode returns in detail.

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 100%, so each parameter (including the omit-to-list semantics of newsId/fileId and truncation via maxChars) is already documented in the schema. The description reinforces the mode-dependent usage but adds no syntax or format detail beyond the schema, which is the baseline-3 case.

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 ('Read the files an instructor attached to an announcement') and gives concrete examples of such files. It is clearly distinguishable from the sibling get_assignment_files (assignments vs announcements) and download_file.

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?

Explicitly states when to use it ('Use this when the user asks what a file attached to an announcement says'), names the alternative download_file and the exact condition that selects it ('when the user wants the file saved to disk'). It also documents the two-step call pattern (courseId to list, newsId+fileId to read).

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