calendar_get_event_details

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns detailed info including attendees and description, but does not mention potential errors (e.g., event not found), authentication needs, or whether any side effects occur. As a read-only operation, the lack of mutation-related disclosure is less critical, but the description remains somewhat minimal.

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 a single, front-loaded sentence with no redundant words. It directly conveys the tool's purpose and key return content, making it easy to parse quickly.

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?

This is a simple tool with only two parameters and no output schema. The description mentions attendees and description but does not give a complete picture of the returned details (e.g., start time, location, status). Without an output schema, the description should more fully enumerate what 'detailed information' includes, but it covers the most notable fields.

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 describes both parameters (event_id and calendar_id) clearly, achieving 100% schema description coverage. The description adds no extra parameter-level detail beyond what the schema already provides, so the baseline score 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 clearly states the tool retrieves detailed information about a single event, with the specific inclusion of attendees and description. This distinguishes it from sibling tools like calendar_query_events (which queries events) and clearly indicates the resource (event) and action (get details).

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 phrase 'a single event' implies this tool is for retrieving one event by ID, but the description does not explicitly state when to prefer this over alternatives like calendar_query_events or calendar_find_free_slots. No exclusions or alternative suggestions are provided.

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