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. It reveals that the default is the current week and that filtering by date range or single day is possible. However, it does not describe the returned data structure, pagination, timezone handling, or whether only basic event details are returned.

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 two sentences, front-loaded with the core purpose and containing zero fluff. It conveys the main action, the default behavior, and the available filtering options efficiently.

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 simple read-only listing tool with three optional parameters and no output schema, the description provides sufficient context to invoke it correctly: default behavior and parameter use. It could be improved by mentioning what event fields are returned, but this is not critical for basic invocation.

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 100%, with all three parameters (date, startDate, endDate) already explained in the schema. The description adds only minimal value by reinforcing that a range or single day can be specified, which is essentially redundant with 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 states a specific verb and resource: 'Lista eventos de Google Calendar' (lists Google Calendar events). It clearly distinguishes this tool from siblings like create_event, reschedule_event, and delete_or_cancel_event, which all involve other actions. The default behavior and optional filters are also stated.

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 implies usage by explaining the default current-week behavior and acceptable parameters (date range or single day). However, it does not explicitly compare with alternatives or state when not to use this tool, leaving the agent to infer when to choose list_events over siblings like detect_conflicts or find_free_slots.

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