get-calendar-event-list

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

Annotations already declare readOnly/idempotent/openWorld, so safety is covered. The description adds real behavioral context beyond that: the list excludes event bodies and attendees, and subscription calendars are not included — non-obvious exclusions an agent would otherwise miss.

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?

Front-loads required parameters and the range constraint, then filters, then examples. The bullet structure and inline examples each carry distinct information without 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?

No output schema exists, and the description compensates by listing the returned event fields (id, calendar, subject, startedAt, endedAt, wholeDayFlag, location, category, recurrenceType), so an agent knows the shape of the result and the exclusions.

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 100%, so baseline is 3, but the description adds meaning beyond the schema: it glosses the postType enum values in human terms (toMe = I am an attendee, etc.), explains the category enum (general/post/milestone), and clarifies calendars defaults to all.

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?

States a specific verb and resource ('Get Dooray calendar events (일정 목록) in a time range') and distinguishes itself from the sibling get-calendar-event by noting the list omits body and attendees and pointing to that tool for details.

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?

Explicitly names required parameters (timeMin inclusive, timeMax exclusive), the 1-year range constraint, and the exact alternative to use for full event details. Filter semantics and two worked examples remove any ambiguity about how to invoke it.

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