upcoming

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

No annotations exist, so the description carries the full burden of explaining behavior. It states the filtering criteria but does not disclose whether results include due dates, how assignments are organized, whether only the count or full details are returned, or how the days parameter affects the range.

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 extremely concise and communicates the core selection criteria in a single sentence. It is front-loaded and easy to scan, though it omits parameter and return-format details that could have been included without much length.

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?

With no annotationsasi and no output schema, the description must be self-sufficientam. It fails to explain the 'days' parameter, result format, default behavior, or how this tool compares to 'list_assignments' and 'overdue'. A simple listing tool still needs at least parameter and return-value context.

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 is one parameter, 'days', with 0% schema description coverage. The description mentions a 1–31 day range but never explicitly maps this to the 'days' parameter or explains how changing it alters results. The parameter semantics are therefore largely left to inference.

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 identifies a specific resource—unsubmitted assignments—and a clear time window (next 1–31 days) across enrolled courses. It is distinguishable from siblings such as overdue and list_assignments, though it lacks an explicit verb like 'list' or 'get'.

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 when to use the tool (for future-due unsubmitted assignments) but provides no explicit guidance on when to choose it over list_assignments, overdue, or grades. It does not name alternatives or exclusion conditions.

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