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

The annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine behaviour beyond them: the content of the result changes by role, with students seeing hand-in status and released results while lecturers see submission counts and feedback backlog. That is meaningful context for interpreting output; only pagination/ordering behaviour is left unstated.

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 zero filler: the primary list action is front-loaded and the role-dependent visibility detail follows. Every clause conveys information an agent cannot get from the schema or annotations.

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 single-parameter, read-only listing tool with no output schema, the description does the important work by explaining what the rows represent and how they differ by viewer role. It does not mention ordering, pagination, or what a task entry contains beyond deadlines and submission/feedback status, which is a modest gap rather than a blocker.

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% and the single courseId parameter is documented with its origin ('from list_courses'), so the schema carries the parameter burden. The description adds nothing about courseId or its format, which is acceptable at this coverage level but earns only the baseline.

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 opens with a specific verb+resource ('Lists a Course's Tasks with their deadlines'), which distinguishes it from the singular get_task sibling without needing to name it. The role-dependent payload (submission status for students, counts for lecturers) further pins down what the tool is for. It stops short of an explicit contrast with an alternative tool, so it lands just below the top mark.

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?

There is no statement of when to use this tool versus get_task, course_files, or get_course_page, and no prerequisites or scoping advice beyond the schema's note that courseId comes from list_courses. The intended audience (student vs lecturer) is described only as a property of the response, not as a selection condition. An agent must infer the usage context entirely.

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