read_assignment_attachment

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

The annotation readOnlyHint is false, implying the operation may have side effects, but the description says 'Read or download' which suggests a read-only action. This is a direct contradiction. The description also does not disclose any potential side effects, permissions, or other behavioral traits, leaving the agent with a misleading impression.

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 description is a single, efficient sentence that front-loads the core purpose and includes a helpful pointer for obtaining the file ID. There is no wasted wording.

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 tool with 6 parameters and no output schema, the description leaves significant gaps. It does not clarify the behavior of the optional parameters, the return format, or any side effects, and it contradicts the readOnlyHint annotation. The agent would need to infer too much to use it correctly.

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?

The schema covers only 50% of parameters (courseId, assignmentId, fileId have descriptions), and the description adds the crucial detail that file IDs come from list_assignments/get_assignment, which is useful. However, it does not explain the optional parameters offset, download, and maxChars, which are also undocumented in the schema. The description only partially compensates for the missing schema coverage.

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 the verb (read/download) and the resource (attachment belonging to a specific assignment), and it even directs the agent to obtain file IDs from list_assignments/get_assignment. It does not explicitly differentiate from siblings like read_announcement_attachment or read_my_submission_file, but the resource scope is unambiguous.

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?

It tells the agent where to get the file ID (from list_assignments/get_assignment), which provides context for using the tool. However, it does not state when to prefer this tool over other attachment-reading tools, nor does it mention any exclusions or prerequisites beyond the ID source.

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