events_upcoming

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

No annotations provided, so description bears full burden. Only states it 'lists' events, implying read-only, but does not disclose if it is non-destructive, what fields are returned, or any limitations like pagination. Lacks behavioral context.

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?

Extremely concise: one sentence for purpose, then bullet-style argument descriptions. No fluff, front-loaded with main action. Every word earns its place.

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?

Given output schema exists (but not visible), description does not need return values. However, for a list tool, it omits common context like ordering, maximum results, or whether it supports pagination. Adequate for basic use but not fully 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 has 0% description coverage, but description fully compensates by explaining each parameter's format (YYYY-MM-DD) and defaults (today, 30 days from today) for start/end dates, and allowed values ('2025' or '2026') for year. Adds meaningful usage information beyond 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?

Description clearly states 'List upcoming Acme events in a date range' with a specific verb and resource. It distinguishes from sibling tools like events_search (which likely searches by criteria) and events_detail (which gets details of one event).

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?

Provides defaults for date range (today to 30 days), implying typical use case. However, no explicit guidance on when not to use or alternatives among sibling events tools (e.g., events_search, events_attendee_schedule).

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