Get League By Slug

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

The annotations already establish that the operation is read-only, idempotent, non-destructive, and open-world, while the description confirms a single-resource retrieval. It adds no further context about missing slugs, not-found behavior, data freshness, or the returned league representation.

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 single sentence is front-loaded, grammatical, and contains no filler. Its brevity is appropriate for a simple one-parameter lookup, with selection and behavioral omissions assessed separately.

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?

The schema and annotations provide nearly everything needed to invoke this simple read operation correctly. With no output schema, however, a brief result overview and not-found behavior would improve completeness, as would explicit routing from get_all_leagues for slug discovery.

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%, and the required string parameter is already documented as “League slug,” so the baseline score applies. The description adds no slug syntax, example, case-sensitivity rule, or source for obtaining valid slugs.

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?

“Retrieve a league by its slug” clearly states the verb, resource, and lookup key. It implies a single-league lookup but does not explicitly distinguish the tool from siblings such as get_all_leagues or get_sport_by_slug.

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 phrase “by its slug” implies that the tool is appropriate when the caller already knows a league slug. There is no explicit guidance on when to prefer get_all_leagues for discovery or get_events_by_league_slug for retrieving events.

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