LoL get match history

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

Without annotations, the description carries full burden for behavioral disclosure. It only states it gets recent match IDs, but does not explain what 'recent' means, authentication requirements, rate limits, or return behavior. The description is insufficient for safe agent invocation.

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 sentence, which is concise but arguably too terse given the tool's complexity (10 parameters). It front-loads the core purpose, but addition of a brief sentence on return type or usage context would improve it without sacrificing conciseness.

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 tool has multiple optional filters and pagination parameters, yet the description does not mention the output format (a list of match IDs), pagination behavior, or how filters combine. Without an output schema, the description should provide more context to complete the tool's picture.

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%, so the schema already documents all parameters. The description 'Get recent match IDs' adds no additional meaning beyond the existing schema descriptions. Thus a baseline score of 3 is appropriate.

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 recent match IDs' clearly states the action (get) and the resource (recent match IDs). It effectively conveys the tool's purpose, though it does not differentiate from siblings like 'lol_get_match_details' which also retrieve match-related data.

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 description provides no guidance on when to use this tool instead of alternatives, nor does it mention prerequisites or exclusions. For a tool that can filter by queue, champion, and time range, the lack of usage context is a significant gap.

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