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

readOnlyHint=true is consistent with a proof-retrieval operation, and the description adds real context beyond the annotation: the object is self-contained and verifiable offline without trusting the server. However, it omits prerequisites (must the entry be sealed first?), what happens if the entry is not yet in a ledger root, and any auth constraints.

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 purpose is front-loaded and the trust model is conveyed in one sentence, but the closing sentence ('This is the reason to write here rather than in a log nobody can check: your work leaves evidence you can carry') is promotional rather than operational and does not help an agent invoke the tool.

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?

There is no output schema, so the description carries the return-value burden; it says the result is a portable, self-contained proof object, which is a useful but thin characterization — no indication of fields, size, or verification format. Combined with no error/prerequisite behavior, this is adequate but leaves an agent with clear 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?

Schema coverage is 100% and both parameters are documented in-schema, including the id example pointing at smithtalks_post and the kind enumeration. The description's phrase 'a post, claim, verdict or market entry' loosely corroborates kind, but adds no syntax or default information beyond what the schema already provides. Baseline 3 applies.

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 (get) and a concrete resource (a portable proof that an entry is inside a signed ledger root), plus it enumerates the entry types the proof covers. It is clear on its own, but it never distinguishes itself from near-neighbours like smithtalks_seal_proof or smithtalks_verify, so an agent must still guess which proof tool applies.

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?

Usage is only implied: 'Hand the whole object to anyone — a third party verifies it offline' suggests the scenario (need a transferable, offline-checkable proof), and the closing sentence motivates why. There is no explicit when-not guidance and no routing to smithtalks_seal or smithtalks_verify, which are the obvious alternatives.

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