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

readOnlyHint=true already tells the agent this is a safe read, and the description correctly reads as reference material with no side effects, so nothing is contradicted. It adds content scope (canonical form, hash, calldata, step-by-step checks) but no operational detail such as whether the returned steps are chain-specific or versioned.

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?

A single front-loaded sentence that leads with the agent's goal ('verify a sealed delivery claim yourself') and then lists the sections covered. It is dense but every clause names real content, with only mild run-on compression.

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 zero-parameter documentation tool with an output schema, the description covers what the document contains, so an agent knows roughly what it will get back. What is missing is positioning within the cluster of sibling spec and status tools, which matters here because several near-identical names exist.

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 there is nothing the description needs to disambiguate; baseline 4 applies. The description correctly implies a parameterless lookup rather than a filtered query.

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 enumerates the content (canonical form, hash, opBNB calldata layout, check semantics, repeatable steps), which tells an agent this is a verification reference document. But it never says outright that the tool returns a spec, and it does not distinguish itself from the many sibling spec tools (proof_spec, receipt_spec, attest_spec, mev_flow_spec).

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?

There is no 'use this when...' guidance, no exclusions, and no pointer to the alternatives an agent should consider instead. The phrase 'verify a sealed delivery claim yourself' implies a context, but the relationship to delivery_status or verified_delivery is left to inference.

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