upcoming_assignments

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

Annotations already cover readOnly/idempotent/openWorld/destructive, so the burden is lower. The description adds the ordering guarantee, timezone handling ('student's timezone'), and the status enumeration, which are useful beyond annotations. It does not mention pagination or result caps, a minor gap given the output schema exists.

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?

Front-loaded with the core verb and the practical use case ('what's due this week?'), followed by supporting details. Every sentence earns its place; no filler.

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?

Output schema exists, so return-shape explanation is unnecessary. Annotations cover safety. The description is complete for an agent to select and invoke the tool, with only course_id and pagination as minor omissions.

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 0%, so the description must compensate. It explains `days` (window), `include_submitted` (hide finished work), and implies `course_id` scoping, though course_id is not explicitly documented. Three params with two well-covered and one implied is above the 3 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?

States a specific verb+resource (assignments due within N days), the ordering (by due date), and the payload (submission status, points, URL). It also positions itself against siblings with 'the one call to make for what's due this week,' distinguishing it from upcoming_events and overdue_assignments.

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?

Explicitly names the intent ('what's due this week?') and the alternative behavior via include_submitted=false. The behavioral toggle is spelled out with the condition that selects it.

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