Query LCU OpenAPI/Swagger schema

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

No annotations are provided, so the description carries the full behavioral burden. 'Live' implies the spec is fetched from the running client rather than a static file, but the description does not state whether a fetch hits the network, whether results are cached, refresh cost, or that it is a read-only operation. For a zero-annotation tool this leaves important behavioral gaps.

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?

A single well-formed sentence, front-loaded with the intent. No padding or repetition, though it could have used a second clause to route the agent to alternatives.

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?

There is no output schema and no annotations, so the description must carry more weight, yet it does not describe the shape of results (endpoint list vs. single signature vs. model definition) or how the optional filters combine. Adequate for basic invocation but incomplete for an introspection 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?

Schema description coverage is 100%, so all four parameters already have clear descriptions with examples (e.g. path '/lol-lobby/v2/lobby', model 'LolLobbyLobbyDto', method enum). The description adds nothing beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Inspect') and a concrete resource set ('LCU API endpoint signatures, parameters, request bodies, and models'). An agent understands what the tool returns, but nothing distinguishes it from siblings like lol_endpoints or lol_get, which plausibly overlap in the discovery space.

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?

There is no when-to-use or when-not-to-use guidance. 'the client's live OpenAPI/Swagger v2 specification' hints that it is a discovery/introspection step, but the description never says to call it before crafting lol_request calls, nor how it relates to lol_endpoints or lol_get.

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