canvas_upcoming_events

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond the annotations: the time window is about a week, there is no date filtering input, and long descriptions are shortened. It could say more about ordering or pagination behavior, but the core behavior is clear.

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?

Three compact sentences with no wasted wording. The scope and the alternative tool are front-loaded for quick scanning.

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 simple read-only list tool with no output schema, the description covers the time window, cross-course scope, truncation behavior, and the alternative for date-range use. Combined with complete schema descriptions and safety annotations, an agent has enough information to call it 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 raw and page parameters are already documented in the schema. The description does not mention those parameters or add syntax beyond the schema, though it does clarify that no date input is available. Baseline 3 is appropriate when the schema carries parameter semantics.

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?

States a specific resource and scope: upcoming calendar events and assignment deadlines across all courses, matching Canvas's "Coming up" list. It also distinguishes itself from canvas_planner by noting that this tool has no date input and covers about the next week.

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?

Explicitly defines the default usage context (approximately the next week, no date input) and names the alternative tool, canvas_planner, for a chosen date range. An agent can choose between the two without further inference.

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