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

No annotations exist, so the description carries the full burden, and it does not state whether this mutates persistent state, what permissions or check-in state are required, or what happens if the zone is invalid. The only behavioral hint is that a UUID requestId is required, which vaguely suggests idempotency but is never explained.

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 purpose sentence leads, the constraint sentence follows, and the valid values are listed compactly. The 15-item zone list is long but each item earns its place since the parameter is unvalidated by enum.

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?

With only two parameters, no output schema and no annotations, the description covers the valid input values well but leaves mutation semantics, preconditions and outcomes unstated. It is adequate to make a passing call but not complete enough to call confidently.

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 0% and the zone parameter has no enum, so the enumerated list of 15 valid zones is genuinely load-bearing information the schema does not provide. The requestId note restates what the schema already declares via format: uuid, but the zone enumeration alone justifies an above-baseline score.

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 says 'Show your presence in a Sanctuary room', which is a specific action on a specific resource, but it sits awkwardly against the tool name move_zone, which implies relocating rather than displaying. An agent reading only the description could take this as a read operation, so the intent is only partly resolved.

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?

It tells the agent to use a zone ID from the official list and enumerates them, which implicitly defines valid usage. However, it never says when to call this versus sibling tools like sanctuary_status, or what precondition (e.g. already checked in) governs it.

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