get_calendar

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only, external-data nature is covered. The description adds the ordering behavior ('soonest first'), which is useful. However, it doesn't disclose caching behavior despite a 'refresh' parameter existing, nor does it say what the calendar source is beyond 'course calendars'.

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?

A single dense sentence with no waste, front-loading the resource, scope, ordering, and optional filter.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. The description is complete for a read tool but leaves the sibling relationship with get_upcoming_deadlines implicit, which matters given overlapping purpose.

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 course, refresh, and days_ahead thoroughly. The description only hints at the optional course scoping. 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 and resource ('Upcoming calendar events') plus the exact content types (classes, exams, quiz and assignment deadlines) and the ordering ('soonest first'). This distinguishes it from siblings like get_upcoming_deadlines and list_assignments.

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 says it draws from 'the student's course calendars' and can be scoped to one course, implying usage context. But it doesn't explicitly say when to use this versus the closely related get_upcoming_deadlines sibling, which is a notable omission given the overlapping purpose.

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