Get a person’s calendar for one year

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description reinforces 'READ-ONLY' and adds behavioral details: returns scheduled_minutes and events, filter affects response, and required scope. No contradictions. Description adds significant context beyond 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?

Description is two sentences plus a scope and read-only note. No redundant information. Every sentence is informative.

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 sufficiently explains what the tool returns (days with scheduled_minutes and events). It covers filtering and required scope. Could elaborate on output format, but for a simple retrieval tool it is adequate.

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 100% with all three parameters described. Description adds value by explaining that 'all' is the default for filter and advising to use days_with_events to keep response small. This goes beyond the schema's enum description.

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 it gets a person's calendar for one year, listing days with scheduled_minutes and events. It also mentions filtering with days_with_events. This distinguishes it from sibling tools like get_day_calendar and get_month_calendar.

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?

Description provides guidance to use days_with_events filter to keep response small, and states required scope. It implies the use case (yearly calendar) but does not explicitly exclude other tools like month or day calendars. Clear context but no explicit 'when not to use'.

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