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

Annotations already establish the safe read profile (readOnly, idempotent, non-destructive), so the bar is lower; the description adds real behavioral context beyond them — external fetches through public IPFS gateways, network-dependent outcomes, and the fact that the Registry holds only a CID pointer, never content.

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?

Front-loads the purpose, then the two input modes, then the motivating gap. Dense but every sentence carries information; slightly long but not padded.

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?

With no output schema, the description supplies the return shape (reachable true/false, bytes fetched, answering gateway) and the on-chain-vs-IPFS distinction an agent needs to interpret results. Nothing material is missing for a read-only diagnostics tool with fully documented params.

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 both parameters are already documented (including CID format examples). The description adds only marginal semantics (username resolves the pointer via the Registry contract), which justifies a baseline 3 rather than more.

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?

States a specific verb and resource ('Check whether a blockpage's profile content is actually retrievable from IPFS') and explicitly positions itself as 'the pin-status companion to lookup_blockpage,' letting an agent separate it from that sibling without opening either schema.

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?

Gives clear selection context: pass a username (resolves on-chain CID) or a CID directly, and frames the use case as closing the gap between on-chain pointer resolution and actual content loading. The sibling relationship is named, though there is no explicit 'do not use this when…' exclusion.

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