canvas_get_upcoming

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

No annotations are provided, so the description carries the full burden. 'Get' clearly signals a read operation and 'authenticated user' provides context, but the description does not disclose return format, pagination, or whether any special permissions beyond authentication are required. It is not misleading, but it is not deeply transparent.

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 a single, focused sentence with no filler. The core purpose, scoping, and user context are front-loaded and easy to parse.

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 the zero-parameter schema and low complexity, the description is largely complete for invoking the tool correctly. It states what will be returned (upcoming events and assignment deadlines) and for whom, though it could specify the exact meaning of 'upcoming' and the response shape more precisely.

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 has zero parameters, so there is no parameter semantics burden. The schema is trivially complete, and the description does not need to explain inputs. The baseline of 4 applies here.

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 ('get') and a specific resource ('upcoming events and assignment deadlines'), scoped to the authenticated user. It is distinguishable from siblings like canvas_list_assignments through the 'upcoming' and 'deadline' focus, though it does not explicitly contrast itself with those alternatives.

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 'upcoming' qualifier implies this tool is for time-sensitive events and deadlines rather than general listings, but the description gives no explicit guidance on when to choose this over canvas_list_courses or canvas_list_assignments. Usage context is implied rather than stated.

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