Google Calendar MCP Server

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

With no annotations provided, the description carries the full burden. It discloses that the tool 'Returns full event details' and 'Requires the event ID', which are useful behavioral traits. However, it lacks information about permissions, rate limits, error handling, or whether it's a read-only operation (though implied by 'Get').

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 front-loaded with the core purpose in the first sentence, followed by supporting details in a concise list format. Every sentence adds value: the first states the action, the second elaborates on returns, and the third specifies prerequisites. No wasted words.

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 the tool's moderate complexity (retrieve operation with 2 parameters), no annotations, and no output schema, the description is reasonably complete. It covers purpose, return details, and prerequisites. However, it could improve by mentioning authentication needs or response format, but the lack of output schema is partially compensated by listing return attributes.

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 fully documents both parameters. The description adds marginal value by mentioning 'Requires the event ID' (implied required parameter) but does not provide additional semantics beyond what the schema descriptions state for event_id and calendar_id.

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 explicitly states the verb 'Get' and resource 'detailed information about a specific calendar event', clearly distinguishing it from siblings like calendar_list_events (list multiple events) or calendar_update_event (modify events). It specifies the scope as 'full event details' including specific attributes like title and attendees.

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 provides clear context for when to use this tool: to retrieve detailed information for a specific event identified by its ID. It implicitly suggests alternatives like calendar_list_events for listing events or calendar_search for finding events, but does not explicitly state when NOT to use it or name specific alternatives.

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