get_deadlines

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real scope detail — overdue items are included but capped at the last 2 weeks — which is behavior beyond the annotations. It says nothing about return shape, ordering, or how the days window interacts with the fixed 2-week lookback.

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?

A single front-loaded sentence with no filler; the parenthetical examples are the only mild redundancy. Efficient and easy to scan.

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 and 0% parameter coverage, the description should explain what the two parameters do and roughly what is returned. It gives a rough sense of contents but leaves both parameters and the returned fields undocumented, so an agent cannot call it precisely.

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 0%, so the description carries the full burden for the two parameters and largely fails: 'days' (default 30) is never explained, and 'course' (nullable filter) is never mentioned. The 'last 2 weeks' phrase relates to a fixed overdue window, not to the days parameter, so an agent gets no help sizing the query.

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?

Names a concrete resource (deadlines/actions to do) with examples (assignments, quizzes) and states the time scope, so an agent can distinguish it from list_courses or get_announcements without opening a schema. It is clear but does not explicitly contrast itself with any sibling tool.

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?

No guidance on when to call this versus get_announcements, check_updates, or get_course_outline, and no mention of how the days/course parameters change the scope. Usage can only be inferred from the phrase 'upcoming deadlines'.

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