Get Upcoming Events

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

The description discloses critical non-obvious behavior beyond the readOnlyHint/openWorldHint annotations: the hard server-side caps (~1 week, 20 events), their non-adjustability, and silent truncation. This is highly valuable for an agent and does not contradict 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?

Two sentences, each purposeful: the first defines the action, the second provides crucial limitations and an alternative. No redundant wording, perfectly 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 zero-parameter read-only tool with no output schema, the description fully covers purpose, scope, limitations, and alternative behavior. It is complete enough for an agent to decide when to use it and what to expect.

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 tool has zero parameters, so the empty input schema is complete. The description clarifies the implicit 'current user' context, which is useful. Baseline for 0 parameters is 4, and no further parameter info is needed.

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 the tool's function: 'Get the current user's upcoming calendar events and assignments.' This is a specific verb-resource pair and distinguishes from siblings like list_calendar_events by noting the cap and suggesting an alternative.

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?

It provides explicit guidance on when not to use: 'For a longer or specific date range, use list_calendar_events with explicit start_date/end_date instead.' This explicitly names the alternative and the condition for choosing it.

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