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

The description asserts "READ-ONLY: mutations refused" for a tool whose annotations declare readOnlyHint=false and which is explicitly a create operation. With annotations present, this clause directly contradicts them rather than adding context, and no other behavioral detail (name uniqueness, idempotency, effect of the genesis beacon) is given.

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?

It is brief and front-loaded, but the second sentence is actively harmful — a parenthetical that contradicts the tool's own function and annotations. Brevity does not compensate for a clause that misleads the caller.

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 creation tool with no output schema and an annotation profile covering mutability, the description should confirm what is created and any naming/precondition constraints. Instead it leaves the agent unsure whether the call will succeed at all, since the text claims mutations are refused.

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% and both parameters (name, description) have their own constraints documented, so the description need not elaborate. It adds nothing about parameter meaning, which is acceptable at this coverage level.

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?

"Establish a new sovereign galaxy namespace with an initial genesis beacon" gives a specific create verb and resource, distinct from galaxy.fork and galaxy.list. The wording is slightly ornamental ("sovereign", "genesis beacon"), but the operation is identifiable.

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 statement of when to use this versus galaxy.fork (clone an existing galaxy) or galaxy.list, despite those siblings being obvious alternatives. The only contextual clause is a self-contradictory parenthetical that gives no actionable routing guidance.

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