list_assignments

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

The description discloses what is returned (due_at, points_possible, description, submission types) and that results are ordered by due date. However, it does not specify sort direction, pagination, authentication needs, or any side effects. With no annotations, the description carries the burden but only partially addresses behavior.

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 sentence that conveys the core functionality without redundancy. It is appropriately sized for the tool's purpose.

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?

Given the lack of an output schema, the description should more fully explain return values and behavior. It lists only a few fields (likely incomplete) and omits important details like pagination, error handling, or what happens if the course_id is invalid.

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 0% and the description adds no meaning for the parameters. It does not explain that course_id can be a string or number, nor what limit controls (e.g., max number of assignments returned).

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 'List' and resource 'assignments for a course', and specifies ordering by due date. It is distinct from siblings like get_assignment (single) and list_courses (different resource).

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 on when to use this tool versus alternatives such as get_assignment or list_my_submissions. No mention of prerequisites or when not to use.

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