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

Read-only and idempotence are already in annotations, but the description adds useful behavioral detail: unverified tokens reveal no traits, and the optional parameters verify claimed-page proof. This is extra value beyond the structured metadata and does not contradict the annotations.

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 description is two tight sentences with no redundant expansion of the tool name or title. The primary result is front-loaded, followed only by the important behavior caveat about unverified tokens and optional verification.

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 read-only tool with an output schema and annotations, the description covers the core call path and optional verification behavior. The phrase 'claimed-page proof' is somewhat terse, but the agent has enough context to select and invoke the tool correctly.

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 schema already describes tokenId and owner, and the description adds meaning to the optional parameters by explaining that owner and transactionHash are used for verifying claimed-page proof. This is particularly helpful because transactionHash has no schema description and its pattern alone would be insufficient.

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 definition states a specific verb and resource: 'Read one NFH portrait URL and live Ethereum claim state.' It also signals the tool's unique capability among sibling getters by mentioning the NFT portrait URL and optional chain verification. This distinguishes it from other get_agent_* tools without needing to open their schemas.

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 clear context: use this for reading portrait URL and live claim state, and use the optional owner/transactionHash fields when proof verification is needed. It does not explicitly name alternative tools or say when not to use it, but the use case is sharply defined enough for an agent to decide.

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