list_assignments

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one real behavioral fact — that deadline and submission-status data may be absent ('cuando estén disponibles') — but says nothing about scope (all assignments vs. upcoming), ordering, or result size.

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?

A single front-loaded sentence with no repetition of the tool name or title. The trailing 'cuando estén disponibles' is slightly soft but earns its place as a data-availability caveat.

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 one-parameter read tool with full schema coverage and annotations, the description is adequate: purpose and partial return contents are stated. It is still missing differentiation from get_assignment/get_deadlines, which matters given a crowded sibling set in the same course/assignment domain.

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 course_id property already explains ID/URL/name forms and ambiguity handling. The description only implies the parameter by saying 'de una materia específica'; baseline 3 applies.

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 (list) and resource (assignments/tasks of a course) and adds what is returned (deadlines, submission status). It does not distinguish itself from close siblings such as get_assignment (detail view) or get_deadlines, which share part of the same domain.

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?

The description says nothing about when to call this instead of get_assignment or get_deadlines, nor about prerequisites. The only routing hint (course_id comes from list_courses) lives in the schema, not the description.

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