Upcoming due dates

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

Beyond readOnlyHint/openWorldHint, the description discloses the 50-item cap, 60-day window, soonest-first ordering, included fields (course name, due date), and the exclusion of course events. That is rich behavior context the annotations do not carry.

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 answer is front-loaded, with the purpose, scope, return shape, parameter behavior, and intent-routing example all in a compact sequence. Each sentence adds something an agent needs.

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 one optional parameter, no output schema, and read-only/open-world annotations, the description covers everything needed: result limits, time window, ordering, fields, exclusions, and default parameter behavior.

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 low, but the description compensates fully: course_ids is an optional array that limits the list, and omitting it covers all current courses. That adds meaning beyond the JSON schema, which only defines the array type.

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 states a specific verb and resource ('Lists up to 50 items due in the next 60 days') with scope, ordering, and exclusions, so an agent can distinguish it from siblings like get_overdue or get_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?

It gives clear context via the 'what is due soon?' framing and the 'still need action' filter, and explicitly excludes course events. It does not, however, name alternative tools such as get_overdue or state when not to use this one.

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