get_calendar_events

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

With no annotations, the description should explicitly state that this is a read-only operation, but it does not. It only describes the return format, omitting behavioral traits like side effects, idempotency, or permissions needed.

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 short and to the point, with structured Args and Returns sections. The JSON snippet is somewhat verbose but useful. No extraneous content.

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 no output schema, the description partially explains the return structure but omits field details and assumptions (e.g., time range filtering). The tool's position among many sibling tools calls for clearer context, which is missing.

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 single parameter 'course_id' is described as 'Canvas course ID', which adds modest meaning beyond the schema title 'Course Id'. However, with 0% schema description coverage, the description does not fully compensate (e.g., no hint on how to obtain the ID).

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 retrieves calendar events for a course, which is a specific verb and resource. It distinguishes from sibling tools focused on other resources like assignments or announcements.

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 provided on when to use this tool vs alternatives (e.g., get_todo, get_all_upcoming). There is no mention of when not to use it or prerequisites like requiring a valid course_id.

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