Get Calendar Events

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

With no annotations, the description carries the full burden and does disclose useful defaults (7-day window, from=now) and the reason includeGenerated is off by default. However it says nothing about ordering, pagination, result limits, or what an empty window returns, and doesn't address permission/auth needs. Solid on defaults, thin on output behavior.

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?

Front-loaded with the verb and resource, and the usage trigger comes after the scoping details. The long em-dash enumeration of event types is informative but slightly padded; a shorter list would carry the same routing value.

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 fetch tool with no output schema and no annotations, the description covers scope, defaults, and cross-tool routing adequately. It doesn't describe the shape of returned events, but the core calling decision is well supported.

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 schema already documents all four parameters including the ISO 8601 format and defaults. The description restates the 7-day default window but adds no format or syntax detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (Fetch) and resource (course calendar events), and enumerates the event types it returns (exams, midterms, labs, recitations, review sessions, schedule changes, instructor-typed deadlines). It also distinguishes the scope (all courses vs one course) from sibling list-style tools, so an agent can pick it without opening the schema.

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?

Gives explicit trigger conditions: 'Use this when the user asks when an exam is, what's on their calendar, or what's happening this week.' The includeGenerated param description routes the agent away from this tool for assignment/quiz/discussion due dates toward get_upcoming_due_dates and get_assignments. Lacks an explicit 'when not to use' for the main calendar surface, but the routing is clear.

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