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

With no annotations at all, the description carries the full behavioral burden and does so well: exact price ($5.00 USDC on Solana), what is and is not written on-chain ('those two hashes — and nothing else from the verdict'), irreversibility ('public and permanent'), and failure handling (owed write completes on retry with the same payment, no second charge; otherwise refunded). Cost, mutability, and failure semantics are all disclosed.

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?

It is a single dense paragraph of roughly 150 words that opens with the price rather than the action, forcing the agent to read several clauses before learning what the tool does. The retry/refund clause is valuable, but the pricing and permanence material is packed tightly enough that the actionable sentence is easy to lose. Nothing is pure filler, but the ordering is not 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?

For a paid, irreversible write with no output schema, the description covers cost, prerequisites, on-chain visibility, and failure/refund behavior — the dimensions an agent most needs before committing money. The notable gap is what the call returns (transaction signature, memo address, or confirmation status), which is not described anywhere since there is no output schema.

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 description coverage is 100%, so the two parameters are already documented in the schema with the same wording ('the verdict hash from the issued verdict', 'the submission SHA-256 from an issued verdict's coverage block'). The description restates this provenance but adds no format, encoding, or validation detail beyond the schema. 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?

The description names a specific verb and resource: the service writes two hashes (submission SHA-256 and verdict hash) to Solana in a single memo transaction, producing one anchored receipt for one Memory Provenance Audit verdict. That is enough to distinguish it from provenance_criteria and the audit/pre-check flow, which it explicitly says are HTTP-only. The core action is buried mid-sentence behind pricing detail, so it is clear but not crisp.

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?

It states the prerequisite plainly — you must already hold an issued verdict and supply its two hashes — and it routes the agent away from using this tool to run the audit or pre-check by giving the separate HTTP endpoint. It does not state explicit when-not conditions (for example, behavior when the verdict was issued by another service), but the context is clear.

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