account_by_riot_idRiot ID → account/puuid.
| Name | Required | Description | Default |
|---|---|---|---|
| region | Yes | americas | europe | asia | |
| tag_line | Yes | ||
| game_name | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| puuid | No | Player UUID | |
| tagLine | No | Riot tag line | |
| gameName | No | Riot game name |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds no behavioral context beyond the annotations, such as error handling, rate limits, or authentication needs. It is a missed opportunity to add value.
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 extremely concise (4 words), which is good for brevity but lacks structure. It front-loads the purpose but omits any elaboration. It earns its place but could be expanded slightly for clarity.
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 presence of an output schema, the return values are covered. However, the description does not mention what happens when the Riot ID is not found, any prerequisites (e.g., valid region), or the relationship to other tools. Incomplete for a tool with 3 parameters.
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 coverage is only 33%, yet the description does not clarify the 'tag_line' and 'game_name' parameters beyond the schema. The description does not compensate for the low coverage; it simply omits any parameter details.
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 'Riot ID → account/puuid.' clearly indicates the tool converts a Riot ID to an account/puuid. The verb is implied (convert/resolve), and the resource is specific. It distinguishes from the sibling 'account_by_puuid' which likely does the reverse.
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 on when to use this tool versus alternatives like 'account_by_puuid'. The description does not mention any prerequisites, limitations, or preferred contexts. The agent is left to 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.
Add one secure layer between your agents and this server.
Several tools have overlapping purposes: champion_mastery and summoner_top_mastery both return mastery data, and the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) plus deep_research all handle question-answering. The inclusion of an entire unrelated Pipeworx research suite under a Riot Games server creates cross-domain ambiguity, making it difficult to know which tool to select.
Most tools use snake_case, but the pattern varies: resource_by_key (account_by_puuid), verb_noun (generate_llms_txt, compare_entities), bare verbs (forget, recall, remember), and standalone nouns (match, status). Pipeworx and polymarket tools share consistent prefixes, but the Riot tools and meta-tools break the pattern, resulting in a mixed but still readable convention.
42 tools is far above the typical 3-15 for a focused server. Only 10 are Riot Games-specific; the remaining 28 are unrelated Pipeworx, data-research, Polymarket, and memory tools. The excessive count dilutes the server's purpose and makes it feel bloated.
The Riot Games domain is covered reasonably well with accounts, summoners, mastery, matches, and rankings, but misses common endpoints like champion static data and live match info. The extensive non-Riot tools do not fill these gaps and instead add an unrelated, separately complete surface that distracts from the server's apparent purpose.