Get Calendar

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

The description provides the HTTP method, endpoint pattern, and required OAuth scope 'calendars.readonly', which adds useful context beyond the readOnlyHint annotation. It does not describe error behavior or return format, but the annotations already establish the safe, read-only, idempotent nature of the operation.

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 short and front-loads the core behavior ('Get calendar by ID') before adding the endpoint and scope. The opening 'Get Calendar' is slightly redundant with the title, but the overall structure is efficient.

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 simple, single-required-parameter read-only getter, the description is largely complete: it names the resource, the lookup key, the endpoint, and the auth scope. It could be stronger by explicitly routing users away from this tool when they need to list calendars or retrieve calendar events.

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 input schema has 100% description coverage for the only parameter, calendarId, so the description does not need to add much. It simply reinforces that the calendar is fetched by ID but provides no additional format, validation, or usage nuance beyond the 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?

The description states a clear action and target: 'Get calendar by ID'. It includes the HTTP GET endpoint and specifies that this tool fetches a single calendar, which distinguishes it from list-oriented siblings like calendars_get_calendars.

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 implies the tool should be used when a calendarId is available, but it does not explicitly state when to use this tool versus alternatives. It also does not mention that listing calendars without an ID should use calendars_get_calendars.

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