calendar_get_event

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

With no annotations, the description carries full burden for behavioral disclosure. It fails to mention auth requirements, rate limits, error handling (e.g., behavior for nonexistent uid), or what 'full event' entails. The description is too minimal for safe invocation.

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?

A single sentence of 6 words. It is front-loaded and to the point, but slightly under-specifies for a tool with no output schema. However, for a simple get operation, it remains appropriately sized.

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 simplicity (2 params, no output schema, no annotations), the description is incomplete. It does not explain the return value structure, what 'full event' includes, or potential errors. A get tool with no output schema should describe what is returned.

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 coverage is 50% (calendar param has description, uid param does not). The tool description adds no meaning beyond the schema; it only reiterates 'by uid' without explaining uid format or usage. The undocumented uid parameter lacks any description, and the tool description does not compensate.

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?

Description 'Get full event by uid' clearly states the verb (get), resource (event), qualifier (full indicating complete details), and lookup method (by uid). It effectively distinguishes from sibling tools like calendar_list_events (lists events with summary) and calendar_search_events (searches by criteria).

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?

No guidance on when to use this tool versus alternatives. The description lacks context for when to choose calendar_get_event over calendar_list_events or calendar_search_events, and no prerequisites or limitations are mentioned.

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