get_deadlines

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

No annotations are provided, so the description carries the entire behavioral burden. It does not say whether a Courseweb session/cookie is required (siblings set_session_cookie and interactive_login suggest authentication is a real concern), how far ahead 'upcoming' reaches, whether results span all courses, or how they are ordered, so an agent cannot predict the call's behavior.

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 that names the action, the data, and the source with no filler. It is efficient, though the brevity is partly under-specification rather than tightness.

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 parameters, no output schema, and no annotations, the description is the sole carrier of context. It covers what is returned at a high level but leaves the time window of 'upcoming', authentication requirements, and result shape unspecified, which is adequate but not complete for a data-fetching tool.

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?

The tool takes zero parameters and the schema is an empty object, so there is nothing for the description to compensate for. Baseline 4 applies; no parameter semantics are missing.

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 (Fetch) plus a clear resource (upcoming assignment deadlines and events) and even names the source system, Courseweb. It is distinguishable from siblings like get_announcements or check_assignment_status by the 'deadlines and events' framing, but it never explicitly addresses those near-neighbors, so it falls short of a 5.

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 only usage signal is the word 'upcoming', which implies a forward-looking planning use case. There is no statement of when to prefer this over get_announcements or check_assignment_status, no prerequisites, and no exclusions.

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