canvas_list_calendar_events

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

Annotations already state readOnlyHint=true, so the tool is a safe read operation. The description adds that results are scoped to selected contexts, but does not disclose return format, pagination, or how the 'type' parameter filters events vs assignments. No contradiction with annotations.

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, concise sentence that front-loads the main verb and resource. It is not bloated, but it is somewhat minimal and does not make full use of the available space to add useful context.

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?

With five optional parameters, no output schema, and only a terse one-sentence description, the tool is under-documented. The description gives a high-level purpose but lacks necessary context about parameter combinations, default behavior, return value structure, and edge cases.

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 only 40%, with only startDate and contextCodes having descriptions. The tool description does not explain the 'type', 'endDate', or 'allEvents' parameters, and only loosely hints at contextCodes via 'selected contexts'. It fails to compensate for the schema gaps.

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 lists Canvas calendar events or assignments for selected contexts. It distinguishes the resource as calendar-related, though it does not explicitly contrast with sibling tools like canvas_list_assignments or canvas_list_upcoming_events.

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?

No guidance is given on when to use this tool versus alternatives. The phrase 'across selected contexts' implies the use of contextCodes, but there are no explicit exclusions, prerequisites, or alternative recommendations.

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