calendars_get_calendar

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. However, the description adds no behavioral context beyond that—no mention of return format, fields, or error handling. It fails to disclose anything about what the tool returns or any nuances.

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?

The description is under-specified rather than concisely informative. It is only two words, which is too sparse to be useful. It does not earn its place by conveying necessary details; it is closer to a stub than a concise description.

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 tool that fetches a single resource, the description lacks essential context: what fields are returned, whether it requires special permissions, or what a 'calendar' represents. It is not complete enough for an agent to understand the tool's behavior, despite the simple interface.

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 fully covers the single parameter (calendarId) with a description 'Calendar Id' at 100% coverage. The description adds no additional meaning about the parameter, but since the schema already provides the necessary info, the baseline of 3 is appropriate.

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 'Get Calendar' states a clear verb and resource, but it lacks specificity about what a 'calendar' is in this context and does not differentiate from sibling tools like calendars_get_calendars (plural) or other calendar-related getters. It is not a tautology but is minimal and generic.

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 guidance on when to use this tool versus alternatives. No mention that it retrieves a single calendar by ID, or that calendars_get_calendars should be used for listing. The description provides zero context for tool selection.

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