get_upcoming_deadlines

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

With no annotations, the description carries the full behavioral burden. It does not define what 'upcoming' means (time window, horizon), whether results are sorted, or whether the call is a safe read — the read-only nature is only implied by 'Get'. A significant gap for a query tool whose name hinges on a temporal qualifier.

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?

Compact and front-loaded with the core purpose first, then the single parameter. The raw 'Args:' formatting is a minor stylistic artifact but wastes no space.

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?

An output schema exists, so return values need not be explained. For a one-parameter query tool this is close to adequate, but the undefined 'upcoming' window is a real gap an agent would need resolved before trusting the results.

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 must compensate, and it does minimally: it explains that 'subject' is an optional subject name used to filter deadlines. It does not clarify matching behavior (exact vs. substring, case sensitivity) or what happens when the parameter is omitted.

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 clear verb+resource ('Get college assignment deadlines') and the resource is distinguishable from siblings like calculate_cgpa and search_notes. However, the central qualifier in the tool name — 'upcoming' — is never explained in the description, leaving the temporal scope unspecified.

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 when-to-use, when-not-to-use, or alternative-tool guidance is given. The only usage hint is that subject is an optional filter, which is inferred rather than stated as a usage condition.

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