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

With no annotations present, the description carries the full burden; '[PUBLIC READ]' usefully discloses that this is a non-mutating, public read operation, which is real value. However, it says nothing about side effects, whether the check is expensive, or whether authKey is needed versus optional (the schema marks zero required parameters).

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 compact sentence with the access-level tag front-loaded, so the safety signal is seen first. No filler, though the vocabulary is dense domain jargon that assumes familiarity with Organs and the Human evaluation layer.

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?

There is no output schema and no annotations, so the description should say roughly what a readiness result looks like (counts, lists, boolean flags), but it does not. For a short read-only check the bar is low, yet the undefined domain terms leave the return shape entirely to inference.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents authKey as an optional 'User or admin auth key'. The description adds no semantics about how auth level changes results, so the baseline of 3 applies.

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?

Uses a specific verb ('Check') plus a precisely scoped resource: clusters ready for Organ promotion and Organs ready for the Human evaluation layer. This is distinguishable from promote_to_organ (which performs promotion) and auto_evolve_hierarchy (which acts on hierarchy), though it never names those siblings directly.

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 phrasing 'ready for Organ promotion' implies this is a pre-flight check before calling promote_to_organ, but no explicit when/when-not guidance or alternative is stated. The '[PUBLIC READ]' tag hints at a safe inspection step, yet nothing tells the agent when this check is required versus optional.

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