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

Annotations only give readOnlyHint and openWorldHint; the description adds substantive context beyond them: the result is signed by the service's on-chain delegated key, carries a receipt, is verifiable against the chain, is free, and is data rather than instructions. This is a genuine behavioral disclosure. It doesn't cover latency or rate behavior, so not 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?

The core purpose is front-loaded, but the text carries boilerplate noise: a bracketed '[quorum]' tag, a long service address, and a 'not instructions' disclaimer. These earn their place for provenance but dilute the concise statement of what the tool does.

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 usefully spells out the return shape ({contract, tokenId, owner, blockPinned}) and the verification path. Combined with the defaults in the schema, an agent has enough to call and interpret the result; only usage routing remains thin.

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 schema already documents contract, tokenId, and the block parameter (number|'finalized'|'safe'|'latest', default finalized). The description adds only the concept of block-pinning, which is already conveyed by the schema, so 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 states a specific verb+resource: 'Owner of an ERC-721 token, pinned to one block,' which is unambiguous and distinct enough from tokenInfo/tokenBalance that an agent can select it. It doesn't explicitly contrast itself with those siblings, though the ERC-721 ownership framing makes the distinction implicit.

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 implied by the name and the 'ERC-721 token ownership' framing, but there is no explicit when-to-use guidance and no when-not or alternative routing (e.g., vs tokenInfo or blockNumber). The context needed to choose it is inferable but not stated.

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