List Events

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

Description discloses a key behavioral trait: ISO 8601 inputs with timezone offsets or Z are converted to local naive datetimes for AppleScript. This goes beyond the readOnlyHint annotation, but does not cover all potential behaviors (e.g., pagination, error handling).

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?

Two efficient sentences: the first states the core purpose, the second adds critical behavioral context. No extraneous words; maintains a clear, front-loaded structure.

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?

While the output schema presumably details return values, the description omits explanation for 'limit' and 'calendar_uid' parameters, leaving gaps in understanding for a tool with 4 parameters.

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?

The description only explains 'time range' for start/end, but does not clarify the 'limit' or 'calendar_uid' parameters. With 0% schema description coverage, the description fails to provide adequate semantic meaning for all 4 parameters.

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?

Description explicitly states 'List calendar events overlapping an ISO 8601 time range,' providing a specific verb, resource, and constraint that clearly distinguishes it from sibling tools like calendar_events_for_date or calendar_search.

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 usage context is implied: to list events over a time range. However, there is no guidance on when to use this vs alternatives, nor any exclusion criteria or best practices, receiving the baseline 'implied usage' score.

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