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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds genuinely non-obvious interpretive context: a role SATISFIED means bound in the registry, not a judgment about the cell — a caveat an agent could easily get wrong. It omits cost, rate, or freshness characteristics, which keeps it from a 5.

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?

Content is dense but load-bearing, with no filler sentences. However, the first sentence is a single run-on with deep parenthetical nesting, which makes it hard to parse on first read. It would benefit from being split into the three flow components it actually describes.

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?

An output schema exists, so the description needn't explain return shapes, yet it spends most of its length enumerating returned content instead of covering what the schema can't: when to call it. Domain terms (paradigm, authority, registry, ERC-8489) are used without any gloss, leaving an agent to infer meaning from the schema alone.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is an empty object at full coverage, and the description correctly implies a parameterless snapshot read.

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 enumerates concrete content: the cell's own channel (id, paradigm, authority, state, transport bindings, held roles, anchors, disclosures), the market channel with the cell's admitted and historical roles plus current eligibility, and the world's registries. That is a specific resource inventory rather than a restatement of the name. It stops short of distinguishing this from siblings like flow_roles or cell_status, which cover adjacent role/state territory.

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 to call this versus flow_roles (roles) or cell_status (cell state), even though the described content overlaps both. No prerequisites, no invocation context, no exclusions. The closing sentence clarifies semantics but gives no routing guidance.

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