canvas_list_calendar_events

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

No annotations are provided, so the description carries the burden; 'List' implies a read-only operation but this is never stated. It does add genuinely useful behavioral detail — that an empty start_date falls back to Canvas's default window — but omits pagination, rate limits, and permission requirements.

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 one-line purpose is front-loaded before the Args block, and each parameter line adds distinct information without redundancy. The formatting is terse and scannable.

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?

An output schema exists, so return values need not be explained. Combined with full parameter documentation and the default-window note, the description gives an agent enough to call the tool correctly; only pagination/return-volume expectations are unaddressed.

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 0%, yet the description documents all four parameters: course_id defaults to CANVAS_DEFAULT_COURSE_ID, start_date/end_date use YYYY-MM-DD format, and include_assignments pulls in due dates. This compensates well for the empty schema descriptions, though it could clarify the default date window size.

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 verb and resource ('List calendar events') and scopes it to a course, with an optional expansion ('and optionally assignment due dates'). It is clearly distinguishable from canvas_create_calendar_event and canvas_list_assignments by implication, though it never names a sibling 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 scope ('for a course') and the include_assignments flag suggests the assignment-due-date alternative, but there is no explicit when-to-use guidance or statement of when to prefer canvas_list_assignments or canvas_get_assignment instead.

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