LoL get match details

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

No annotations provided, description does not disclose behavioral traits such as rate limits, data size, what 'detailed info' includes, or any side effects. For a tool with no annotations, this is insufficient.

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?

Single concise sentence, no extraneous information, front-loaded with key action and resource.

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?

No output schema, no annotations, description is minimal. It lacks details on return format or what 'detailed info' entails. Given the tool's potential complexity (match details), the description is incomplete.

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 100% (both parameters described in schema), baseline is 3. Description adds no extra meaning beyond parameter names and defaults; e.g., doesn't explain format of matchIds or region values.

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?

Description clearly states purpose: 'Get detailed info for one or more matches'. Verb is specific, resource is explicit, and it distinguishes from siblings like match_history (lists matches) and match_timeline (timeline events).

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?

Implies usage for retrieving details of known match IDs, but no explicit guidance on when to use vs. siblings like match_history or match_timeline, and no mention of prerequisites or alternatives.

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