Get Upcoming Due Dates

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

With no annotations, the description carries the full burden. It discloses the scope of results (calendar events, assignments, quizzes, exams) and an important limitation (excludes lecture/tutorial materials), adding context beyond the name. It doesn't mention ordering or read-only behavior, but for a retrieval tool this is a reasonable level of transparency.

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?

The description is two sentences, front-loaded with the core purpose and followed by usage examples and alternatives. It is concise, structured, and contains no fluff.

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?

The tool has only two parameters, full schema descriptions, and an output schema. The description covers the primary use cases, exclusions, and a complementary sibling tool. It is complete for an agent to select and invoke the tool correctly.

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 100%, so the baseline is 3. The description does not add parameter-specific details beyond the schema, though it implicitly references courseId via 'for a course'. The schema already documents parameters effectively.

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 uses the specific verb 'Get' and clearly identifies the resource: 'upcoming calendar events and due dates (assignments, quizzes, exams) for a course'. It also explicitly distinguishes itself from siblings by stating it does not list lecture/tutorial materials and references get_content.

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 provides concrete example questions ('What is due this week?', 'When is the next deadline?') that indicate when to use the tool. It also gives an explicit exclusion ('does not list lecture/tutorial materials') and suggests an alternative tool ('pair it with get_content'), offering complete usage guidance.

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