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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond annotations: it fetches bytes through public IPFS gateways, resolves usernames via the Registry contract, and clarifies the Registry stores only a CID pointer — no auth, rate-limit, or failure-mode notes, though.

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?

Purpose is front-loaded and the sentences are dense with useful specifics. The final 'closes the gap' sentence is somewhat rhetorical padding, keeping it from a 5.

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 carries the return-value burden and does so well (reachable true/false, bytes fetched, which gateway answered). It omits edge-case behavior — unverifiable CID, no params supplied, gateway timeouts — leaving a small gap for a network-dependent tool.

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 coverage is 100%, so the baseline is 3, but the description adds meaning: the username path resolves the on-chain CID pointer via the Registry while cid is a direct lookup, clarifying the either/or intent of two optional params. It doesn't state precedence if both are supplied.

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+resource: check whether a blockpage's profile content is retrievable from IPFS. It explicitly positions itself against the sibling lookup_blockpage as the 'pin-status companion,' so an agent can distinguish resolution from retrievability 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 operating context ('pass a username … or a CID directly') and frames its role relative to lookup_blockpage. It lacks an explicit exclusion (e.g. when NOT to bother checking, or behavior when both params are passed/neither), so it stops short of full when/when-not guidance.

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