Tomorrow's Events

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

Annotations already declare readOnlyHint=true, and the description's 'List' aligns. However, the description does not disclose additional behavioral traits like calendar filtering via calendar_uid, pagination limits, or whether all calendars are included by default. It adds minimal value beyond annotations.

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, front-loaded sentence with no waste. It is concise, though it could include brief parameter notes without harming conciseness. The structure is adequate for a simple list tool.

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?

With two parameters (0% schema coverage) and many sibling tools (e.g., calendar_today, calendar_events_for_date), the description is too minimal. It does not explain how to filter by calendar_uid or limit results, nor does it differentiate from similar date-based list tools. The output schema exists but does not compensate for missing parameter usage.

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 0%, but the description does not explain the two parameters (limit, calendar_uid). Parameter names offer some hints, but the description fails to add explicit meaning or usage context, leaving the agent without sufficient guidance for parameter values.

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 'List tomorrow's calendar events' specifies a clear verb (List) and resource (tomorrow's calendar events), distinguishing it from siblings like calendar_today and calendar_events_for_date by the specific timeframe.

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 explicit guidance on when to use this tool versus alternatives, such as calendar_events_for_date with a date parameter, or calendar_today. Usage is only implied (for tomorrow's events), without exclusions or references to other tools.

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