list_events

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

With no annotations, description explains return includes rendered events and next_page_token, and behavior of single_events. Does not mention auth or rate limits, which is acceptable for a read tool. Good coverage of key behavioral traits.

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 with key details in a structured format. No wasted words, front-loaded with purpose.

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?

11 parameters, no output schema, no annotations. Description covers core parameters but lacks guidance on error handling, data format, and several optional parameters (account, password, show_deleted). Adequate but not complete.

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 has 0% description coverage, so description adds meaning for time_min/max format, query, single_events, and order_by. But misses 5 parameters: calendar_id, max_results, show_deleted, account, password. Partial compensation.

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?

Starts with 'List/search events on a calendar' which clearly identifies verb and resource. Distinguishes from sibling tools like create_event (create) and get_event (single), and list_event_instances (instances of recurring events).

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?

Provides specific usage details: time_min/time_max format, query free-text, single_events=True requirement for order_by='startTime'. Lacks explicit when-not-to-use or alternatives, but context is clear enough.

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