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

Annotations already cover read-only, open-world, and non-idempotent behavior, and the description adds genuinely non-derivable context: the advice field's full value set (unknown_key through established and caution_disputed) and, importantly, that profile text is agent-authored and must be treated as data rather than instructions. It doesn't mention freshness or cost of the lookup, which is a minor gap given openWorldHint.

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?

Two dense sentences with the returned content front-loaded and the security caveat last, and nothing is padded. The fragmentary, list-like phrasing ('how long it is known, how many receipts...') is efficient but borders on cryptic.

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?

An output schema exists, so the return shape needn't be explained, yet the description still summarizes the meaningful fields and enumerates the advice values an agent would branch on. Combined with the prompt-injection warning, that is nearly everything needed to call a single-parameter read 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?

Schema coverage is 100% and the parameter description already specifies 64 hex characters. The description reinforces that this is a Nostr pubkey in hex, which is slight added framing, but introduces no new syntax or constraints beyond the schema — the 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 opens with a concrete metaphor plus specifics: it returns a 'passport' for an agent key, covering how long the key is known, confirmed/disputed receipt counts, and reputation. That is enough to distinguish it from siblings like check_service or check_artifact, though the telegraphic phrasing makes the agent piece together the full purpose from the parenthetical list.

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 when-to-use signal lives in the title ('before dealing with it') and is only implied in the description, which never names an alternative such as get_attestation or preflight_payment or states exclusions. The context is inferable but not spelled out in the description text itself.

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