dooray_calendar_events

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

No annotations are present, so the description carries the full burden. It only says 'find', which implies a read-only operation, but it does not disclose details like whether all calendars are included by default, how time boundaries are treated, or what the response structure looks like. This is minimal disclosure.

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 a single, concise sentence that states the core purpose. It is front-loaded and not padded, though it is under-specified and lacks any additional useful structure or detail.

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?

Given the tool has 4 parameters, 3 required, no output schema, and no annotations, the description is too sparse. It fails to explain that timeMin/timeMax are required, that the operation must be 'find_events', or how the optional calendars parameter filters results. This leaves the agent under-informed for correct invocation.

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%, with descriptions for timeMin, timeMax, calendars, and operation. The tool description adds no parameter-specific meaning, but because the schema fully documents parameters, the baseline of 3 applies.

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 the specific verb 'find' and resource 'dooray events of calendars', clearly indicating a read operation on calendar events. It distinguishes from siblings like dooray_calendar_calendars and dooray_calendar_post_event, though it could be more explicit about searching by time range and optional calendar filtering.

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 provides no guidance on when to use this tool versus alternatives such as dooray_calendar_calendars or dooray_calendar_post_event. It does not mention prerequisites, typical scenarios, or that it searches within a time range and optionally filters by calendars.

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