List Calendar Events

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

The description discloses default behaviors (end_date defaults to start_date, start_date defaults to today, type defaults to 'event') and the unbounded nature, which is more than annotations alone provide. No contradiction with annotations (readOnlyHint=true, openWorldHint=true). Could add a note about response format, but not required.

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?

Two sentences, front-loaded with the main purpose, followed by exclusions and default behavior. Every sentence serves a purpose with no redundancy. Exceptionally concise for the amount of information conveyed.

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 the tool's moderate complexity (4 params, one enum, no output schema), the description covers essential usage and defaults. It doesn't detail return structure, but that's not necessary without an output schema. The description is sufficient for an agent to use the tool correctly.

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 schema already covers all parameters (100% coverage), so baseline is 3. The description adds meaningful defaults and usage for end_date, start_date, and type, enhancing understanding beyond the schema. This extra context justifies a score of 4.

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 calendar events for a course, with a specific verb and resource. It explicitly differentiates from siblings by noting the caps on `get_upcoming_events` and `get_my_upcoming_assignments`, making the purpose unmistakable.

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?

The description provides explicit usage context: it explains when to use this tool (when you need more than the ~1-week/20-item caps) and how to extend the default single-day range by passing both start_date and end_date. It also mentions the type parameter for assignment due dates, giving clear directional guidance.

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