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 of behavioral disclosure. 'Upcoming calendar events' only implies a read-only listing operation; it does not reveal sorting, date range behavior, pagination, or what happens when no events exist. The description does not contradict annotations because none exist, but it adds little behavioral depth.

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 three-word description is extremely concise and front-loaded, but it is under-sized for a tool with four parameters and no other documentation. While every word earns its place, the description sacrifices substance for brevity, making it less than 'appropriately sized.'

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?

For a 4-parameter tool with no annotations and no output schema, a single noun phrase is insufficient. The description lacks any information about event fields, ordering, timezone handling, or the meaning of the days parameter, leaving an agent to infer most important details from the schema and tool name.

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 50%, with start and timezone documented in the schema. The description mentions no parameters and does not compensate for the undocumented days and calendar fields. However, the schema already handles half the parameters, making this a borderline case; the description adds no value beyond the 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 'Upcoming calendar events' clearly identifies the resource (calendar events) and the scope (upcoming), which distinguishes it from sibling tools like list_tasks and list_collections. However, it is a noun phrase rather than an explicit verb+resource statement, and it does not explicitly differentiate from search_contacts or list_collections, so it falls short of a 5.

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 list_tasks or search_contacts. There is no mention of context, exclusions, or conditions that would help an agent choose this tool over its siblings.

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