get_calendar_events

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

Discloses return format (JSON array with fields) and a limitation (no events for image/PDF calendars). However, no annotations exist, and description does not mention read-only nature, auth requirements, or side effects. Could be more transparent.

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?

Description is well-structured with a clear first sentence, return info, and fallback note. Slightly wordy with the 'Args:' line, but overall efficient and front-loaded.

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, description covers return format and a practical limitation. Missing error handling and prerequisites, but for a single-param tool, it provides adequate context for usage.

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?

Only parameter 'school_id' is listed with a basic 'School ID' line. The schema provides no description (0% coverage), and the description adds no extra meaning like how to find the ID or valid values. Minimal value beyond schema.

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?

Description clearly states the tool gets calendar events for a school using ICS export. It distinguishes from siblings by noting that some schools use images/PDFs instead and directs to get_feeds/get_post as alternatives.

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 says when to use (to get calendar events) and when not (schools using images/PDFs). Provides clear alternative workflow using get_feeds and get_post, aiding agent decision-making.

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