calendar_multi_get

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

No annotations are present, so the description carries the behavioral burden. It conveys a read-style batch fetch operation through 'fetch' and 'retrieve', implying no destructive side effects. However, it does not address behaviors like partial failure, invalid URL handling, or whether the operation is strictly read-only beyond inference.

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 two short sentences with no filler. The first sentence states purpose, and the second gives usage context. Every part earns its place.

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 simple two-parameter batch fetch tool, the description covers inputs and intended use well. There is no output schema, so the return format is unknown, but 'retrieve their details' gives a sufficient expectation of the result.

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%, so both parameters are already adequately documented. The tool description adds no new parameter-level guidance, such as URL formats or how calendar_url interacts with event_urls, but the schema already carries the meaning.

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 names a precise operation: batch-fetching multiple calendar events using exact event URLs. This clearly separates it from tools like calendar_query or list_events, which find or search for events rather than fetching known URLs.

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 description is explicit about when to use the tool: 'Use when you have exact event URLs and want to retrieve their details.' It does not explicitly name alternatives or state when not to use it, but the usage condition is clear enough.

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