Get Calendar

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and open-world access. The description adds useful context that the operation requires calendar.read and targets the selected mailbox, which is beyond the annotations. It could say more about permission failure behavior or conditional requests, but the added auth requirement is meaningful.

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 waste. It front-loads the action and then states the permission prerequisite, making it easy to scan.

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?

The tool is a simple read operation with full schema coverage, annotations, and an output schema. The description covers purpose and permission needs, though it does not mention conditional ETag/304 behavior or error outcomes; those are adequately represented in the schema and annotations.

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 all three parameters are already documented in the schema. The description's phrase "in the selected mailbox" supports mailbox_id semantics but adds no syntax, format, or edge-case details beyond what the schema provides.

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 uses a specific verb and resource: "Read one calendar." It clearly distinguishes this operation from listing calendars or reading events, but it does not explicitly name sibling tools or contrast their use cases.

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 gives the basic context—reading a single calendar in the selected mailbox—and states the required permission. It does not explain when to prefer this over mailbox_list_calendars, mailbox_get_calendar_event, or other calendar-related siblings, nor does it provide exclusions.

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