Calendar Get Event

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. However, the description adds no behavioral context beyond those annotations, such as what happens when an event ID is invalid or whether delegation-specific authorization is required.

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 short but not meaningfully concise; it spends its single sentence on wrapper boilerplate rather than functional content. This is under-specification rather than economical writing.

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?

Although this is a simple one-parameter read-only tool with an output schema, the description is missing the core statement of what the tool does. It leaves the agent to infer the entire purpose from the tool name and parameter name, which is inadequate even for a low-complexity tool.

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 0%, and the description does not compensate by explaining event_id, its format, or how to obtain a valid value. The only available meaning comes from the parameter name and title, which is insufficient for a low-coverage schema.

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 only restates the tool name and wrapping context: "Delegated Apple domain tool 'calendar_get_event' exposed through Apple-Tools-MCP." It never states that the tool retrieves a calendar event, so it is essentially a tautology with no functional meaning.

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?

There is no guidance on when to use this tool versus alternatives like calendar_list_events or calendar_get_event. The description provides no context about when to select this tool, what prerequisites exist, or when another tool would be more appropriate.

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