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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds two pieces of context they cannot convey: the data is 'self-reported' (a trust/provenance caveat that materially affects how an agent should cite it) and 'No account or key needed' (auth requirements). That is exactly the kind of beyond-schema behavior disclosure this dimension rewards.

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?

Front-loaded with the operative instruction ('Use this to check whether Rightshold is operational'), and the long middle clause is a payload enumeration that earns its space by telling the agent what it can cite. It is dense but not padded; a bulleted split of the contents list would read slightly better than the colon-chained sentence.

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?

With an output schema present, return-format detail is not required, yet the description still summarizes the returned sections well enough to justify a citation. Combined with the auth note, the provenance caveat, and the pointer to an independent verification path, nothing an agent needs in order to call a zero-parameter status tool correctly is missing.

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 no parameter meaning for the description to add or omit. Baseline 4 applies; nothing in the description muddies the empty input contract.

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?

States a specific verb+resource ('check whether Rightshold is operational') and then enumerates exactly what the record contains: component checks (ledger chain, sealing, anchoring, webhooks, storage), ledger/registry counts, 90-day uptime, and incidents. That is far more specific than the title, and it distinguishes the tool from verification siblings by naming check_conformance as a different thing.

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?

Gives an explicit triggering condition ('before you depend on it') and points to an alternative ('check_conformance offers an independent re-check') for callers who need independently verified data. It stops short of stating when NOT to use it or of naming any of the actual sibling tools such as ledger_verify or gate_check, so the routing guidance is clear but not exhaustive.

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