find_events

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It implies a read operation with 'list,' but does not explicitly state it is read-only, mention auth requirements, rate limits, or what happens if no events are found. This is a 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 sentence that is front-loaded with the core purpose ('List events between two datetimes') and includes a concise usage hint. Every word adds value, with no 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?

Given the tool's simplicity (3 params, no output schema), the description covers the basic purpose and provides a use case. However, it does not describe return values (event objects), handle the optional timeZone, or mention any limits, leaving the agent with some ambiguity.

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 merely restates that start and end are ISO datetimes, which is already in the input schema descriptions. The optional timeZone parameter is not mentioned, and with 67% schema coverage, the description fails to add meaningful context 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 clearly states the tool lists events between two datetimes, with a specific verb and resource. It also distinguishes from siblings by noting its use for resolving event IDs before updates or deletions.

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 explicitly tells when to use the tool: 'use this to resolve an event id before updating or deleting.' This provides clear context for selecting this tool over alternatives like update_event or delete_event. However, it does not mention when not to use it, such as for listing all events without a date range.

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