Get Upcoming Due Dates

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 genuinely new context: the enumerable submissionStatus values, that dates are UTC ISO strings, that conversion to local time is required, and that results are date-ordered. Missing pagination/limit behavior, but the added semantic detail is substantial.

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 dense sentences, front-loaded with the core purpose and with no wasted preamble. The inline enum enumeration is long but functional since no output schema exists to carry it.

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 output schema, the description usefully discloses the key return field (submissionStatus values) and the date encoding plus local-time conversion requirement. Combined with 100% schema coverage for inputs, an agent has what it needs; only ordering/pagination specifics are thin.

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%, so both parameters (courseId, daysAhead) are already fully documented in the schema. The description only implicitly gestures at them via 'all courses' and 'date ranges', adding no syntax or format beyond the schema. 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 verb+resource ('upcoming due dates across all courses') with clear scope and even names the sibling it is not (get_todo). An agent can distinguish it from get_assignments and export_due_dates_calendar without opening a schema.

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 explicit usage ('for deadlines, what's due and date ranges') and routes the agent away with a named alternative and condition ('For advice on what to do first, use get_todo instead'). Nothing is left to inference.

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