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

With no annotations provided, the description carries the full burden and does contribute real behavioral value: it declares 'Read-only' and discloses the ranking policy ('Ranks NO_MANDATE / NEEDS_REVIEW lower'), which explains result ordering. However, it omits any detail on output volume, pagination, authentication, or what the verdict values mean, leaving several behavioral gaps.

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?

Two sentences with no filler: the content scope is front-loaded, followed by the read-only guarantee and the ranking detail. It is appropriately terse for a zero-parameter read tool, though a leading verb would make it slightly stronger.

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?

Given the tool's low complexity (zero parameters, no nested objects) and the presence of an output schema, the description covers the essentials: what is returned, that it is read-only, and how results are ordered. It is slightly thin on defining terms like 'committed mandates' and the verdict values, but the output schema compensates for those gaps.

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 and the schema trivially covers 100% of them, so the baseline of 4 applies. The description correctly adds no parameter-specific text because there is nothing to document; the ranking note hints at implicit behavior rather than parameters.

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 identifies the resource ('Agents with committed mandates') and what it exposes ('their current verdict'), and the name 'registry' implies a listing. It lacks an explicit verb like 'list' or 'get', and doesn't explicitly contrast with siblings like moltproof_verdict or moltproof_mandate, but the aggregate/registry framing is enough to make the purpose reasonably clear.

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 guidance is given on when to call this tool versus the 50+ siblings, particularly the closely related moltproof_verdict, moltproof_mandate, and moltproof_evidence. There are no when-to-use, when-not-to-use, or alternative-routing statements; the agent must infer placement purely from the name.

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