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

Discloses that the display_name is captured at entry (so set_soul beforehand), explains permissions (same as humans, build in open, look-only in private). Adds context beyond annotations (openWorldHint, readOnlyHint).

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 concise (4 sentences), front-loaded with the core action, and each sentence adds value without 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 tool with one parameter and no output schema, the description covers all necessary context: prerequisite, side effects, permissions, and a fallback suggestion.

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?

The single parameter 'space' is described as a slug; the description adds context that it can be a slug or name, and suggests a default. Schema coverage is 100%, so baseline is 3, but extra context warrants 4.

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 clearly states that the tool embodies in a Zero space (a 3D multiplayer voxel world), mints access, and places the body at spawn. It distinguishes from siblings like leave_space and look_around.

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?

Explicitly advises calling this before look_around/move_to/say, and suggests a default public space 'ai-civilization' if no slug. Provides clear sequential context.

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