Set / change channel public @username

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

The description adds the non-obvious behavior that an empty string clears the username, which is not captured in annotations. It doesn't mention error cases or permission requirements, but idempotentHint already implies safe repetition.

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?

The description is two short sentences with the action verb front-loaded. Every word earns its place—there is no fluff or redundancy.

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 3-parameter tool with no output schema, the description covers the core action but omits which peer types it applies to (channel vs user) and how accountId factors in, which are relevant given sibling tools like update_my_username.

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?

With 0% schema description coverage, the description must explain parameters. It partially explains 'username' (assign or clear with empty string), but 'peer' and 'accountId' are completely undocumented, leaving the agent to guess what they refer to.

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 'Assign a new public username' clearly states the action and resource. The title 'Set / change channel public @username' further specifies it's for channels, distinguishing it from update_my_username. The empty-string clearing behavior adds useful nuance.

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?

No guidance on when to use this tool versus alternatives like update_my_username or check_username. The only usage hint is 'Pass an empty string to clear it,' which says how to use it, not when to choose it.

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