get_events_keys

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

Annotations already provide readOnlyHint, idempotentHint, and non-destructiveHint. The description adds that it returns only keys and minimal bandwidth, which aligns and adds context. No contradictions.

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, 30 words, front-loaded with purpose, examples, and use case. 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?

Combined with schema coverage and annotations, the description adequately explains output form (keys) and use case. Lacks explicit mention of pagination or array structure, but for this simple enumeration it is sufficient.

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?

Input schema covers the single parameter 'year' with full description and constraints. Description mentions 'season year' but adds no new meaning beyond what the schema provides. Baseline at 3 due to 100% schema coverage.

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 explicitly states the tool lists every FRC event key for a season year with concrete examples. It highlights that this is the lightest enumeration, distinguishing it from sibling tools that return full event objects.

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 indicates this tool is for lightweight enumeration useful for driving subsequent per-event queries, implying it should be used when only keys are needed. Sibling tools like get_events and get_events_simple provide more detail, but it does not explicitly state when not to use it.

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