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

The readOnlyHint: true annotation already covers the safety profile, and the description adds useful behavioral context: it mentions that private task access follows current source permissions and that the read includes accessible submissions and assignments. This goes beyond what the annotation alone conveys.

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 short sentences with no filler. The main read target is front-loaded, and the permission nuance is added in the second sentence. Every part contributes useful information.

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-only operation with a single required parameter, the description sufficiently states what is returned (task, accessible submissions, assignments) and the permission model. It does not detail error behavior or output structure, but the tool's simplicity and the readOnlyHint annotation make those gaps acceptable.

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 describes the single id parameter as a required UUID, but the description adds no meaning about what the id refers to (task id, submission id, or assignment id). With 0% schema description coverage, the description could have compensated by clarifying the id semantics, but it does not.

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 identifies a specific verb ('Read') and resource ('a task') and expands the scope to accessible submissions and assignments, which distinguishes it from merely listing tasks. It is clear enough for an agent to know what is being read, though it does not explicitly contrast with list_tasks.

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?

No guidance is provided about when to use this tool versus alternatives like list_tasks or read_subject. The description implies usage when you have a task id, but it never states this explicitly or mentions any exclusions.

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