get_events

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

No annotations are provided, so the description bears full burden. While the description indicates data retrieval ('Get statistical data'), it does not disclose behavioral traits such as whether the tool is read-only, rate limits, or what 'statistical data' entails (e.g., aggregated vs raw, or any default sorting).

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, concise sentence that efficiently conveys the tool's purpose and key filtering dimensions. It is front-loaded with the action ('Get statistical data') and resource ('multiple FRC events'). No wasted words.

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?

Context is adequate for a read operation with 10 fully described parameters. However, no output schema exists, so the description should clarify what 'statistical data' means (e.g., counts, averages) or the response structure. The sibling context shows this is part of a complex API, but the description does not address pagination or field selection.

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 coverage is 100%, and the description does not add additional meaning beyond listing filter options (year, location, type, week). For example, 'year' is fully documented in schema; the description does not clarify interactions between filters or default behavior when multiple are provided.

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 gets 'statistical data for multiple FRC events' and lists specific filtering criteria (year, location, type, week). It distinguishes itself from siblings like 'get_event' which likely retrieves a single event, and 'get_team_events' which filters by team.

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 implies usage for listing events with filters, but it does not explicitly state when to use this tool versus alternatives e.g., get_event (for a single event) or get_team_events (when filtering by team). There is no exclusion guidance.

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