Get calendar event

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by specifying that the response includes the full workout description, which tells the agent what to expect beyond basic event fields. No contradiction with annotations.

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 one efficient sentence with the verb and resource front-loaded. It includes valuable distinguishing details (event types, full workout description) without any filler or redundancy.

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 single-parameter read-only tool with comprehensive annotations and an output schema, the description covers all necessary call context: what the entity is, how to select it, and a key detail about the returned data. Nothing critical is missing.

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%, and the id parameter's description in the schema already says 'Event id (from list_events).' The tool description's 'by id' simply restates the schema, adding no new parameter semantics, so the baseline 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 states a precise verb ('Get'), a specific resource ('one calendar event'), and selection by id. It also disambiguates from siblings like list_events and get_workout by naming the event types (planned workout, race, note) and noting the full workout description is included.

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?

Usage context is implied: you call this when you have an event id and want a single event. However, the description does not explicitly contrast with list_events, update_event, or get_workout, nor does it say 'use list_events to find the id first' — that cross-reference only appears in the schema's id description.

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