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

The description goes well beyond the annotations (readOnlyHint, idempotentHint, destructiveHint) by disclosing the signed Nostr event format, the exact verification process (recomputing event id and verifying schnorr signatures), the on-chain settlement with Hyperliquid, and the fact that it includes failures. This gives the agent rich behavioral context that annotations alone cannot convey, with no contradictions.

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?

The description is longer than strictly necessary but well-structured, opening with a concise purpose statement and then layering relevant verification and usage details. Each sentence contributes to the agent's understanding, though the marketing-flavored phrase 'the proof you can trust this verifier WITHOUT trusting us' could be seen as slightly extraneous. It remains focused and front-loaded.

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 there is no output schema, the description fully explains what the tool returns: the full index when called with no args, or a single signed verdict when passed an entry. It also clarifies how to interpret the response (by verifying signatures) and emphasizes the on-chain immutability, making the tool's behavior completely transparent for an agent. This is a well-rounded and complete description for a read-only tool with one optional parameter.

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 provides 100% coverage for the single 'entry' parameter, describing it as optional with an example and noting that omission returns the full index. The description adds little beyond rephrasing this ('Call with no args for the index, or pass entry to read one signed verdict'). Since schema coverage is full, the baseline score of 3 is appropriate.

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 clearly states the tool's function: 'Read invinoveritas's PUBLIC, SIGNED, AUDITABLE verdict track record.' This is a specific verb+resource combination, and the additional context about verifying signatures and immutability makes the purpose unmistakable. It implicitly differentiates from the sibling 'ledger_submit' by being the read-only counterpart, though it does not name it explicitly.

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?

The description provides clear context for when to use this tool—whenever an agent needs to decide whether to trust this verifier, calling it 'the agent-to-agent should I rely on this verifier? primitive.' It also explains invocation patterns ('Call with no args for the index, or pass entry to read one signed verdict'). However, it does not explicitly compare to alternatives or state when not to use it, so it falls short of a 5.

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