get_upcoming_assignments

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

No annotations provided, so description carries the burden. It doesn't explicitly state read-only nature or discuss side effects, but the function is clearly a query. No contradictions.

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?

Extremely concise: two sentences plus Args section. Front-loaded main purpose with no wasted words.

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?

Given low complexity (2 simple params, output schema exists), the description covers essential behavior and parameter semantics. Could mention edge cases like empty results but not critical.

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 description adds meaning to both parameters (course_id optional, defaults to all courses; days_ahead default 14) beyond the schema, which lacks descriptions (0% coverage). It compensates well.

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 clearly states the tool retrieves upcoming assignments due within a time window, with specific verb 'get' and resource 'upcoming assignments'. It distinguishes from siblings like 'complete_assignment' and 'get_grades_detailed'.

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 description explains when to use (for upcoming assignments within a time window) and includes optional filtering by course_id. However, it lacks explicit when-not-to-use or alternative suggestions among siblings.

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