Configure summoner spells in champion select

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

Annotations already declare readOnly false, destructive true, idempotent true, and openWorld, so the safety profile is provided. The description adds mutation scope (player spell slots), the idempotency condition, the prerequisite of an active champion select session, and the required write allowlist endpoint—context beyond the annotations.

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?

Front-loads the action and resource, then usage, alternatives, and operational requirements in compact, labeled sentences. Every sentence earns its place without filler.

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?

For a two-parameter mutation tool with annotation coverage and no output schema, the description supplies prerequisites, idempotency, mutation effect, and sibling alternatives. An agent has enough information to call it correctly and avoid related tools.

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%, so the schema already documents both parameters. The description adds that spell names are case-insensitive and repeats examples of accepted names/IDs, which is a small but useful extension beyond the schema text.

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 (resolves spell names/IDs and updates selection) and resource (summoner spells in champion select). It also explicitly names sibling tools for rune configuration and champion selection/hovering, so an agent can distinguish it without opening schemas.

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?

Explicitly says to use during champion select to equip spells for your role, and routes rune configuration to lol_workflow_runes_set and champion picking/hovering to lol_workflow_champ_select. Conditions and alternatives are fully covered.

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