get_upcoming_deadlines

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

No annotations provided, so description carries full burden. It describes aggregation and sorting, and parameter behavior, but does not explicitly state that it is a read-only operation or other behavioral traits like access scope (all courses vs. specific). Adequate but not comprehensive.

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?

Two sentences: first defines purpose, second explains parameter and adds guidance. Front-loaded, no unnecessary words. Maximally concise for the information needed.

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?

For a low-complexity tool with one optional parameter and no output schema, the description is nearly complete. Could clarify scope (all courses?) but otherwise sufficient.

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%, but description explains the 'days' parameter meaning ('look-ahead window') and its default (30). Adds clear value beyond the schema's minimal type and default.

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?

Clearly states it lists upcoming tasks and deadlines, aggregated from various sources (assignment due dates, quiz closings), sorted by date. References Moodle's 'Timeline', forming a distinct purpose from siblings like list_assignments or list_courses.

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?

Implicitly recommends as 'best single source' for deadlines, but lacks explicit when-not-to-use or alternatives. The guidance is adequate given the tool's simplicity.

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