riot_ranked

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

With no annotations, the description must disclose behavioral traits. It only states 'get ranked stats' without explaining the return format, authentication (api_key field present but not mentioned), rate limits, or data freshness. This is insufficient for a tool with no annotation support.

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 concise (one sentence, 8 words) but is under-specified. It effectively communicates the tool's core purpose without unnecessary words, but it lacks critical details that would justify a higher score for completeness.

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?

Given the tool has 3 parameters, no output schema, and no annotations, the description is minimal. It does not explain what ranked stats include, how to interpret the region parameter, or the purpose of api_key. The absence of output schema increases the need for description completeness, which is unmet.

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 0%, meaning the description adds no meaning to any of the 3 parameters (summonerId, region, api_key). Even the required parameter summonerId is unexplained. The description fails entirely to clarify parameter roles or formats.

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 ranked stats for a League of Legends summoner' clearly states the action (get) and the resource (ranked stats) with the context (League of Legends summoner). It distinguishes from sibling tools like riot_get_match or riot_summoner, which serve different purposes.

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, prerequisites (e.g., needing a summoner ID from riot_summoner), or context like what region values are accepted. The description lacks any usage direction.

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