list_events

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

With no annotations provided, the description carries the full burden. It discloses that the tool queries the calendar and returns a list of matching events. It also explains the exclusive time-bound semantics and the requirement for local time with timezone offset, adding useful behavioral context beyond a simple 'list events' statement.

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 well-structured with an introductory sentence and a clean Args list. It is appropriately sized for a tool with six parameters, and every line conveys relevant 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?

Given the tool's complexity (six optional parameters, no output schema, no annotations), the description covers all essential aspects: parameter semantics, time format requirements, filter combination, and the return type. It provides enough information for an agent to invoke the tool correctly without further documentation.

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 schema has 0% description coverage, so the description fully compensates with a detailed Args section. It explains the meaning of each parameter (summary, description, location, timeMin, timeMax, maxResults) and includes format constraints, adding significant value beyond the raw schema.

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 opens with 'Retrieve a list of calendar events based on specified filters,' which is a specific verb+resource statement. It clearly distinguishes this read-oriented list tool from sibling tools like create_event, delete_event, and update_event.

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 clear context for when to use the tool (when retrieving filtered calendar events) and explains that filters are optional and combinable. However, it does not explicitly mention when not to use it or name alternatives, though sibling tool names make the distinction obvious.

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