get_overdue_assignments

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

The description discloses the filter (past due, unsubmitted) and sorting (most overdue first), which is behavioral. However, with no annotations provided, the description carries the full burden; it does not mention authentication requirements, scope (current user or all courses), or whether it's read-only. The behavior is adequately described for a simple tool.

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 with no redundancy. It efficiently conveys the core functionality without unnecessary words.

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 no parameters, no output schema, and no annotations, the description is minimal but covers the essential behavior. It does not describe the return format (e.g., fields of assignment objects) or scope, which could be added for completeness. For a simple tool, it is adequate but not exhaustive.

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?

There are no parameters in the input schema, so schema coverage is 100%. The description adds value by specifying the filtering and sorting behavior, which defines the tool's semantics. Per guidelines, 0 parameters baseline is 4.

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 it returns assignments that are past due and unsubmitted, sorted by most overdue first. This distinguishes it from siblings like 'get_assignments' which likely returns all assignments, and 'get_upcoming_deadlines' which includes upcoming ones.

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 implies usage for retrieving overdue unsubmitted assignments but does not explicitly provide guidance on when to use this tool versus alternatives like 'get_assignments' or 'get_upcoming_deadlines'. No exclusion criteria or alternatives are mentioned.

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