Update summoner presence and status message

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

Annotations already declare non-read-only, idempotent, destructive, open-world. The description adds genuinely new behavioral context: it mutates friend presence state, is idempotent when re-setting the same status, and requires 'PUT /lol-chat/v1/me' on the write allowlist. It stops short of explaining what is destroyed or whether a missing allowlist entry causes an error.

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?

Purpose and usage are front-loaded in the first two sentences, with the behavioral/allowlist note kept terse at the end. The enum repeat ('chat', 'away', 'dnd', 'mobile') is mildly redundant with the schema but the rest earns its place.

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 tool with no output schema and full schema coverage, the description covers purpose, usage, sibling routing, and the write-allowlist prerequisite — nothing an agent needs in order to call it correctly is missing.

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 both parameters are fully documented in the schema. The description echoes the availability enum and the status-message concept but adds no syntax, defaults, or edge-case semantics beyond that, matching the baseline of 3.

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 (updates) and resource (local player's chat availability and status message), and enumerates the accepted availability values, so the agent knows exactly what the tool acts on.

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 when to use it (setting do-not-disturb, stepping away, broadcasting a custom status) and names the alternative for a different need: 'For sending chat messages to conversations, use lol_chat_send instead.'

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