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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the safety profile is covered. The description adds genuine semantic context beyond that: it defines FRESH ('a routine completed within its interval'), distinguishes registry-held data from node-local data ('what the node keeps beside it'), and explains what the cycle record means. It does not mention staleness of the readings, freshness guarantees, or any auth/permission nuance for querying another subject.

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?

One long dash-chained sentence with a nested colon that buries the actual purpose under an enumeration of return fields; it is not front-loaded with what the tool does or when to call it. The FRESH glossary is useful but arrives mid-sentence as an aside, and the output schema already carries the return shape, so much of the field listing 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 read-only status tool with an output schema and full schema coverage, the description covers the conceptual vocabulary (FRESH/DUE/OVERDUE, cycle, registry vs node-local) reasonably well. It is still incomplete on the two things an agent needs: differentiation from sibling status tools and whether querying another subject is gated. Adequate, not 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% and the single 'subject' parameter is documented in-schema as 'another subject's status (default: this cell)'. The description adds nothing about address format issues, cross-subject visibility restrictions, or what happens if the subject is unknown — baseline 3 for full schema coverage.

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?

Names a specific resource (maintenance registry state for a cell) and enumerates what it returns (enrollment, state version/root, per-layer commitments, timeliness, activity signal, policy, node-side cycle records). But the framing is a list of nouns rather than a verb+resource statement, and it never distinguishes this from close siblings like cell_status or safety_status. An agent can guess it's a status read, but not why it isn't the same as cell_status.

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?

No when-to-use guidance at all: it does not say to call this instead of cell_status or safety_status, nor when timeliness/cycle state matters versus general cell state. The only implicit routing is the 'subject' parameter defaulting to this cell.

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