Get Cancelled Classes

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the useful detail that teacher comments are included in results, but it does not define the 'upcoming' window (how far ahead, whether past cancellations are excluded) or ordering, which are the behaviors that actually matter for this read.

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 packs the resource scope and the returned fields with zero filler. Nothing to trim and nothing important buried.

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 no-parameter read tool with no output schema, describing the returned fields is exactly the right compensation, so an agent knows what it gets back. The one missing piece is the definition of the 'upcoming' time horizon, which affects whether the results meet the caller's need.

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, so there is nothing for the description to disambiguate; baseline 4 applies. The description's field list reinforces that the output is self-contained with no filtering inputs.

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 a specific verb (Retrieve) plus a clearly scoped resource (upcoming cancelled class sessions) and even enumerates the returned fields (time, course, teacher, room, comment). It is clearly distinguishable from siblings like get-schedule or get-calendar, though it never names those siblings explicitly.

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?

Usage is implied by the word 'cancelled' – an agent can infer this is the tool to call when checking for cancelled sessions – but there is no explicit when-to-use, when-not-to-use, or pointer to get-schedule/get-calendar for the non-cancelled case.

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