List events

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond that by enumerating the returned fields (id, title, start/end, location, calendar name), which matters since there is no output schema. It does not disclose ordering or pagination behavior.

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?

Purpose and filters are front-loaded, then usage guidance, then return shape — a sensible order with no filler. Slightly verbose in listing return fields, but each sentence carries distinct 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?

Covers purpose, filters, usage triggers, and return values, and the annotations cover safety, so an agent has what it needs to call this correctly. Minor gaps remain around result ordering and whether the limit truncates silently, but with a fully described schema and no output schema this is close to 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 description coverage is 100%, so every parameter including defaults, ISO format, and the limit bounds is already documented in the schema. The description restates the filter axes (title, date range, calendar name) without adding syntax or semantics beyond them, and never mentions the row limit. Baseline 3 applies.

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?

States a specific verb and resource ('List local calendar events') plus the filter dimensions available, which distinguishes it from siblings like list_calendars (enumerates calendars) and extract_calendar (parses events out of email). An agent can pick this tool without opening the schema.

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?

Gives two concrete when-to-use triggers: checking for existing events before creating one, and verifying a recently added event. It stops short of naming alternatives or exclusions (e.g., when to prefer extract_calendar or add_to_calendar), so it is clear context without full routing.

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