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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, open-world mutation, so the safety profile is covered. The description adds the useful constraint that the target must be on the same server and where the token comes from, but says nothing about failure modes, stale tokens, or what happens to the previous pointer.

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 compact sentence plus a short prerequisite clause, with the core action front-loaded. Every phrase carries information and nothing is redundant.

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 three-parameter mutation with annotations covering its safety profile and no output schema, the description supplies purpose, trigger, and prerequisite. It could say a bit more about the effect on the existing alias pointer, but nothing essential for invoking it 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 coverage is 67%; room_url and alias_url are documented in the schema, but alias_token is not. The description compensates by stating the token must come from parlor_alias, which is genuinely useful provenance information. It adds little else beyond the schema, so baseline 3 is right.

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 and resource ('points an alias at another room') plus the scope constraint 'of the same server'. It implicitly separates itself from the sibling parlor_alias by being the re-pointing operation rather than the creation operation, though it does not name a sibling explicitly.

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?

Gives a clear usage trigger ('after a conversation moved') and names a prerequisite dependency ('needs the alias token from parlor_alias'), which tells the agent it must run parlor_alias first. No explicit when-not or alternative-tool guidance, which keeps it out of the top band.

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