Listar eventos de calendario

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

Annotations already declare readOnlyHint=true, covering the read-only safety profile. The description adds the date-range scope and a concrete ISO 8601 example, but does not disclose return structure, ordering, pagination, or boundary inclusivity.

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 verb and resource. It contains no filler or redundant information.

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 2-parameter listing tool with useful annotations, the description provides enough context for selection and invocation. No output schema exists, so return details are not specified, but 'list events' inherently implies a collection of calendar events.

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 input schema fully documents both parameters with ISO 8601 descriptions, giving a baseline of 3. The description adds value by providing a concrete example with a timezone offset (2026-07-30T00:00:00-05:00), clarifying the expected string format 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 uses the specific verb 'Lista' with the resource 'eventos del calendario' and scopes the operation to a date range in ISO 8601 format. This clearly distinguishes it from sibling tools like create_event, update_event, or list_inbox.

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 date-range condition implies when to use this tool: to retrieve calendar events between two dates. However, it does not explicitly mention alternatives or exclusions, such as 'use get_message for a single message' or 'use today_summary for a daily overview.'

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