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

Beyond the readOnlyHint and idempotentHint annotations, the description reveals that entries are signed Nostr events whose integrity can be recomputed, and that they are append-only and Bitcoin-timestamped, implying immutability. It also states the access model, free and no sign-in, which is useful for an agent deciding whether to call. No contradiction with annotations.

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?

Four sentences, each earning its place: purpose, integrity model, usage, and access/documentation. The most decision-relevant information is front-loaded in the first sentence, and the docs link is a compact pointer rather than bloat.

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 single-optional-parameter read tool with annotations already covering safety and idempotence, the description covers purpose, data model, behavior, access, and documentation. The only omission is a concrete description of the response shape for the index or an entry, but that is partially mitigated by the explicit usage instructions and docs link.

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 input schema already fully documents the optional entry parameter with an example and the omit-for-index behavior, so the baseline is 3. The description restates this behavior rather than adding new parameter-level semantics. No additional syntax or format details are introduced.

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?

Opens with a specific verb and resource: 'Reads invinoveritas's public track record of signed verdicts,' which immediately sets it apart from write/verify siblings like ledger_submit and verify_proof. The addition of 'including ones that turned out wrong' narrows the scope and reinforces that this is an audit/read tool. Clear and unambiguous purpose.

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?

Provides concrete invocation context: no arguments yields the index, passing entry reads a specific record, and access is free with no sign-in. It does not explicitly name alternatives or state when-not-to-use, but the read-only framing makes the appropriate use clear for an agent.

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