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

No annotations exist, so the description carries the full behavioral burden; the '[PRIVATE WRITE]' tag does usefully disclose that this is a mutating, access-restricted operation. However, it says nothing about whether the source cells are consumed or copied, whether the promotion is reversible, or what authorization level is required.

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?

A single sentence with the access/mutation marker front-loaded and zero filler. Nothing in it is redundant.

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 five-parameter mutation with no annotations and no output schema, the description omits the important side effects (fate of the bundled cells, tier implications, return value or resulting identifier). An agent can guess the intent but not the consequences of calling it.

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%, so all five parameters are documented in the schema itself. The description only reinforces that cell_ids are bundled into the Organ; it adds no semantics about the optional title/domain/purpose fields or the authKey beyond what the schema states.

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 uses a specific verb pair ('Promote and bundle') with a clear resource ('related cells into an Organ orchestrator module') and adds the resulting tier. It is understandable on its own, but it never distinguishes itself from nearby creation/hierarchy tools such as create_cell or auto_evolve_hierarchy.

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?

There is no statement of when this tool should be chosen over create_cell or auto_evolve_hierarchy, nor any prerequisite guidance (e.g. that authKey is expected, or what state cells must be in). The agent must infer the trigger condition entirely.

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