get_calendar

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about permissions, whether the result is read-only (inferable only from the name), pagination, ordering, or what happens when no events exist. 'Upcoming' is never defined in the description itself, leaving the time-window behavior opaque.

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 tight sentence with no filler, and the core purpose is front-loaded. It is perhaps too terse given the unstated 'days' parameter, but there is no wasted text.

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 two-parameter tool with no annotations and no output schema, the description should at least define the look-ahead window and note the optional course scoping format. It mentions only one of two parameters and leaves behavioral expectations entirely to inference.

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 0%, so both parameters are undocumented in structured data. The description covers the 'course' filter conceptually but never mentions the 'days' parameter or its default of 14, so it fails to compensate for the coverage gap.

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 ('Return upcoming calendar events') and adds a scoping qualifier ('optionally restricted to one course'). It is distinguishable from list-style siblings like get_assignments or get_announcements, though it does not explicitly contrast itself with the closest sibling, get_upcoming_due.

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?

There is no statement of when to prefer this tool over alternatives such as get_upcoming_due, get_updates, or get_snapshot. The only usage hint is the passive 'optionally restricted to one course', which implies but never states the filtering scenario.

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