Set PoE account name

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

Annotations already communicate that this is not read-only and not destructive. The description adds useful context about why the account name is needed and the OAuth-avoidance benefit, but it does not disclose additional behaviors such as validation, persistence, overwriting of an existing name, or failure modes.

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, efficient sentence that leads with the action, includes concrete examples, and explains the purpose. There is no filler or redundant detail.

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 simple one-parameter setter with no output schema, the description is largely sufficient: it states what is set, why it matters, and what format is expected. It stops short of clarifying when precisely to call it, but the low complexity keeps this from being a significant gap.

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?

The input schema covers the single parameter completely, including format examples. The description repeats those examples but adds no meaning beyond what the schema already provides, so it meets the baseline for high schema coverage.

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 clearly identifies the action ('Set your Path of Exile account name'), the resource being configured, and the downstream benefit (fetching characters and gear from poe.ninja without GGG OAuth). This distinguishes it from sibling tools like set_active_character, which operate on a different concept.

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 gives strong context for when this tool is relevant: when the server needs to fetch characters and gear from poe.ninja without OAuth credentials. It does not explicitly list exclusions or name alternative tools, but the purpose is clear enough for an agent to infer the right situation.

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