calendar_get_event

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

Describes return fields comprehensively (summary, start/end, description, location, recurrence, attendees, organizer). No annotations, but read-only behavior implied by 'get' verb.

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?

Extremely concise: one-sentence overview, clear Args section, and return summary. No superfluous content.

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?

Covers essential input and output details. Output schema exists reducing burden. Lacks error handling info, but for a simple get tool, it's sufficient.

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?

Adds meaning to both parameters: calendar_id explained as 'name or URL path', event_uid as 'from calendar_search_events'. Schema coverage 0% so description compensates well.

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?

Clearly states it retrieves detailed info for a single calendar event by UID. Differentiates from siblings like calendar_search_events (multiple events) and calendar_get_freebusy (availability).

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?

Tells when to use: after getting event_uid from calendar_search_events. Lacks explicit when-not or alternatives but provides clear context.

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