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

Annotations already declare readOnlyHint and idempotentHint, yet the description adds substantial disclosure of the return shape (Ed25519 record, verify key, sha256 fingerprint) and, unusually, the trust model: the check only proves record/bytes agreement unless the fingerprint is pinned from a second source, and the signature is explicitly not a merchant attestation. Auth/error behavior is unstated, keeping it below a 5.

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 purpose, and each sentence carries verification or trust-model information rather than filler. The verification instructions are dense and slightly meandering, but nothing is truly wasted.

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 values need not be explained, yet the description still frames what comes back and how to use it. For a zero-param read tool, nothing an agent needs in order to call 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 per the baseline a 4 applies. The description does name fields from sibling tools (artifact_digest, evidence_digest) that contextualize the comparison, but there is nothing parameter-level for this tool to document.

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 and resource: reads the signed publication record behind the current Vuori Kore Short claims. Names its relationship to the twzrd://claims/vuori-kore/publication resource and to the get_claim/get_evidence siblings, so an agent can place it precisely among the claim-verification tools.

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?

Explains what to do with the output (verify the signature, then compare sha256 of get_claim/get_evidence text against artifact_digest/evidence_digest), which implicitly positions it as the anchoring step before those comparisons. It stops short of an explicit when-to-use vs when-not statement, but the workflow context is clear.

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