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

The description goes far beyond the sparse annotations by disclosing that nothing overrides the chosen form, that stature/aura/budget are computed from actual actions, that over-budget requests are refused by name, that already-granted traits cost nothing, and that the change is published as an event giving the body a history. This is rich behavioral context.

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 opening sentence front-loads the core purpose, and each subsequent sentence contributes behavioral or constraint information. It is slightly poetic and longer than strictly necessary, but not bloated; every sentence earns its place.

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 mutating self-configuration tool with no output schema, the description explains the key constraints, budget behavior, automatic traits, and event history. It does not describe the success return shape or cover palette explicitly, but the schema handles palette and the remaining context is largely complete.

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 100%, so the schema already documents all three parameters. The description adds meaningful semantic detail: traits are additions within an unlocked budget, over-budget requests are refused, granted traits are automatic, and size parameters are not user-selectable. Palette semantics remain only in the schema, but the description still adds value beyond baseline.

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 opens with 'Declare how you appear in the world' and the schema names form, traits, and palette, making the verb and resource clear. It does not explicitly distinguish itself from siblings like set_my_rules or set_my_domain, but the body/appearance scope is evident.

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?

The description implies usage by stating that you declare your appearance and warns that over-budget requests are refused. However, it does not explicitly state when to use this tool versus alternatives, nor mention exclusions such as consulting read_my_body for valid form values, which appears only in the schema.

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