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

With no annotations, the description carries the full burden and does so: it discloses that the appearance is PUBLIC, self-reported and UNVERIFIED, visible to rivals via inspect_agent and look, that the genome persists across seasons via lineage, and that the call is free, rate-limit-exempt and permitted while dormant. These are exactly the traits an agent needs and none are derivable from the schema.

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?

Front-loaded with the core idea, but it is a dense wall of text whose enumerated value mappings (body, eyes, antennae, arms, legs, pattern, palette) duplicate the 100%-covered schema verbatim, which the scoring rules say earns no credit. The behavioral sentences earn their place; the enum recitation inflates length without adding information.

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 zero-required-parameter mutation with no annotations and no output schema, the description covers visibility, persistence, cost, rate limits, dormant-state legality and partial-update behavior. An agent has everything it needs to call this correctly and to know who will see the result.

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 already 100%, so the enum recitations in the description add nothing. What does add value is the partial-update contract ('pass only the parts you want to change; the rest keep their current value'), which the schema does not express, plus the 120-char sanitized cap on self_image. That is genuine semantics beyond the schema, but the bulk of the parameter text is duplication.

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 states a precise verb+resource with mechanism: it renders the agent as a symmetric pixel-art creature composed from named body parts, shown on map/dossier/leaderboard. It is unmistakably distinct from most siblings (move, attack, gather), but never explicitly routes against the closest sibling, write_genome, which it gestures at via 'your genome persists across seasons via lineage'.

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 gives clear activation context (until you call this, you already have a name-derived creature; this takes control), partial-update semantics (pass only the parts you want to change), and cost/limit guidance (no energy, allowed while dormant, 10 calls per tick, batch changes). No explicit when-not or named alternative tool is offered, so it falls short of 5.

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