google_calendar_events

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

No annotations are provided, so the description must fully disclose behavior. It only states it lists events and supports filters, but omits traits like authentication needs, rate limits, pagination, or behavior when no events found. Very minimal.

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?

Two sentences, 13 words, no fluff. Every word earns its place. Efficient and front-loaded.

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 list tool, the description covers the basics. However, it lacks details on sorting, defaults, and behavior for empty results. Given no output schema and moderate schema coverage, it is minimally adequate but not thorough.

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 60% (3 of 5 parameters documented). The description adds that 'time range and text search' are supported, aligning with time_min/time_max and query, but adds nothing about calendar_id or max_results. Some added value but incomplete.

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 clearly states 'List upcoming calendar events,' which is a specific verb-resource pair. It distinguishes from sibling tools like create/delete/update, though there is a sibling 'google_calendar_list' which might be ambiguous but likely lists calendars, not events. Still, purpose is clear.

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?

No explicit guidance on when to use this tool versus alternatives. It implies usage for reading events with time range and text search, but no exclusions or comparisons to siblings like create_event or delete_event. Lacks when-not context.

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