Get Events By League Slug

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered without the description. The description adds one genuinely useful behavioral fact — that the league is resolved to its active series before events are returned — but says nothing about pagination behavior, result ordering, or what happens when a league has no active series.

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 short sentences with no filler, and the essential scoping information comes first. It could be marginally stronger by folding the sibling differentiation into the same opening sentence, but nothing is wasted.

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 read-only lookup with a fully documented nested query object and no output schema, the description covers the core mechanics plus the non-obvious series resolution. The remaining gaps — return shape and pagination semantics — are either minor or handled by the schema.

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 100%, including the nested query object's type, section, limit, offset and excludeEventId fields, so the schema already carries the parameter burden. The description only repeats the slug example ('nfl', 'nba') already present in the schema and adds no meaning about defaults or interplay between the nested fields.

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?

States a specific verb ('Retrieve') and resource ('events for a league'), plus scope ('by its slug') and the internal resolution step ('resolves the league to its active series'). This distinguishes it from get_event_by_slug and get_events, though it never names the closest sibling get_events_by_sport_slug to make the league-vs-sport split explicit.

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?

Usage is only implied: an agent infers it should call this when it holds a league slug rather than a sport slug or a specific event identifier. There is no explicit when-to-use or when-not-to-use guidance and no mention of the alternative sibling that takes a sport slug instead.

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