List my calendar events

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description need not repeat safety. It adds operational details beyond annotations: the default date window (yesterday..+14 days), automatic derivation of course contexts, and the conference exclusion. This enriches the behavioral profile without contradicting 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 compact and front-loaded with purpose, then alternatives, then a cautionary note. Every sentence earns its place, with no redundancy or filler.

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 read-only listing tool with no output schema, the description covers the essential context: what is returned, the default window, automatic scoping, and exclusions. It also names alternatives for different needs. Nothing critical is missing for an agent to decide on and invoke this tool.

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 coverage is 50% (type and courseIds have descriptions; startDate/endDate lack any description). The description adds the default date window but does not specify the expected date format for startDate/endDate, nor does it clarify that they are optional. It partially compensates for the gaps but leaves the syntax ambiguous, so an agent might format dates incorrectly.

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 it lists calendar events and assignment dates across courses, with a specific verb and resource. It differentiates from siblings by mentioning planner for due feed and conferences as separate tools, so an agent can distinguish it immediately.

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 provides when-to-use guidance: 'Use planner for the unified due feed; use this for raw calendar events like office hours.' Also notes an exclusion with an alternative: 'live web conferences do NOT appear here — use canvas_list_conferences for those.' This fully covers when and when not to use the tool.

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