Get All Leagues

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds only the 50-per-page pagination constraint; it says nothing about ordering, total counts, or how iteration through pages should proceed, which matters for a listing endpoint.

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?

A single front-loaded sentence with no filler. It is appropriately sized, though the parenthetical pagination note duplicates schema information rather than adding new context.

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 simple read-only listing tool with full schema coverage and rich annotations, the definition is adequate but thin. It omits what a league record contains, whether results are ordered, and that only pagination controls exist because no filter parameters are offered, leaving the agent to discover these from the schema or first call.

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%, with both limit (max 50, default 50) and offset (default 0) documented in the nested query object, so the baseline is 3. The description merely restates the max-50 limit already present in the schema and adds no meaning about offset semantics or page iteration.

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 uses a specific verb and resource ('Retrieve leagues') and adds a pagination scope. It is clear what the tool returns, but it never distinguishes itself from siblings such as get_league_by_slug or get_events_by_league_slug beyond the plural 'all' in the name.

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?

There is no guidance on when to use this listing tool instead of get_league_by_slug for a single league, nor any mention that no filtering (e.g. by sport) is supported. The agent must infer usage from the name alone.

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