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

With no annotations, the description carries the full behavioral burden. It discloses that the tool is paid ($0.05), that content is 'hashed and forgotten' (privacy-preserving), that a timestamped ledger record is produced, and that payment_tx must be passed after paying. It does not cover failure modes or confirmation behavior, but it provides substantial transparency.

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?

Three short, purposeful sentences with no filler. The description front-loads the critical paid nature, states the core function, then gives the precise input/payment instruction. Minor structural inefficiency: 'PAID $0.05' could be a note after the function, but it is still compact.

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?

The description is solid for a paid tool with no annotations and no output schema: it covers payment, input alternatives, and the ledger effect. However, it does not explain what the caller receives in response, how to obtain or validate the payTo address, or what happens on invalid/insufficient payment. These are meaningful gaps for agent invocation.

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 only 33%, yet the description compensates by explaining that content and hash are alternative inputs and that content is discarded after hashing. It also clarifies the payment_tx requirement, while the schema already describes payment_tx as a Base USDC transfer txHash. It does not define hash format or content constraints, but the core param relationships are clear.

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 states a specific action and outcome: 'Witnessed cryptographic seal: sha256 + timestamp + ledger record.' This clearly identifies the tool as a sealing/witnessing operation and differentiates it from simple pings or queries, though it does not explicitly contrast with siblings like khotem_attest or khotem_receipt.

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 gives operational guidance: 'Provide content (hashed and forgotten) or hash. Pay first, then pass payment_tx.' This explains how to invoke the tool and the required payment flow, but it does not state when to choose this tool over its siblings or when not to use it.

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