Missing assignments

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavioral detail beyond that: the result set is restricted to past-due and unsubmitted items, and the empty-parameter default resolves to 'all active classes'. It stops short of describing result fields or ordering, which keeps it at 4.

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?

Three short sentences, front-loaded with what the tool returns, then the scoping parameter, then invocation cues. Nothing is redundant or padded.

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 optional parameter with full schema coverage and annotations, this covers everything an agent needs to decide and call. The only minor gap is that no return shape is described and no output schema exists, so the agent knows less about what fields come back.

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 coverage is 100%, and the schema already documents that course_ids is optional and that empty means all active classes, plus the pointer to get_my_courses. The description restates that default without adding new semantics, so the baseline 3 is appropriate.

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 resource and a precise filter: past-due work that has not been submitted. It is clearly distinguishable from sibling tools like get_todo, get_upcoming_due_dates, and get_assignments based on the 'overdue' framing alone.

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?

Gives concrete user phrasings ('What's overdue?', 'What am I behind on?') plus the scoping rule (pass course_ids or leave empty for all active classes). No explicit 'when not to use' or named alternative tool, which keeps it just short of a 5.

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