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

Annotations already cover read-only/idempotent/non-destructive, but the description adds two things they cannot: the data is self-reported (a trust caveat that affects how an agent should weight the result) and no credentials are required. It stops short of noting caching, freshness, or rate limits.

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 decision rule and scoped well, but the long comma-separated inventory of components is dense and partially duplicates the output schema. Two short sentences then cleanly deliver the caveat and the alternative.

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 zero-parameter, read-only status tool with an output schema and full annotations, the description covers the remaining burden: when to call it, that the data is self-reported, that no auth is needed, and where to get an independent verification. Nothing an agent needs to invoke it 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 the baseline is 4 and there is nothing the description could add. The enumeration of components is about the response, not about inputs, so it does not raise this score.

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 verb and resource ('check whether Rightshold is operational') and enumerates exactly what the record contains (component checks, ledger/registry counts, 90-day uptime, incident history). It is clearly separable from siblings like check_conformance, which it explicitly positions as the independent alternative.

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?

States the trigger condition ('before you depend on it') and a second use case ('to cite its record'), then names the alternative (check_conformance) with the reason to prefer it. Auth precondition is also stated ('no account or key needed').

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