LoL get league by id

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

No annotations are provided, so the description must fully disclose behavior. It only states 'Get league info', implying a read operation, but does not disclose rate limits, authentication needs, output format, or potential side effects. The description is too minimal for a tool with no annotations.

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 clear sentence, front-loaded with the action and resource. It is concise with no wasted words, though it could benefit from one additional sentence to clarify the return value.

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?

With no output schema, the description should explain what 'league info' includes. It does not. Given the tool's moderate complexity (2 parameters) and the lack of annotations, the description is incomplete for an agent to confidently use this tool.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds no additional meaning beyond what is in the schema: it does not clarify the format of 'leagueId' or the effect of 'platform' (e.g., regional routing).

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 'Get league info by league ID' clearly states the verb ('get'), resource ('league info'), and identifier ('by league ID'). It differentiates from siblings like 'lol_get_league_entries' (which returns entries rather than league metadata) and 'lol_get_league_top' (top of league), but does not explicitly call out these distinctions.

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?

No guidance is provided on when to use this tool versus alternatives such as 'lol_get_league_entries' or 'lol_get_league_top'. There is no mention of prerequisites, context, or exclusions.

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