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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description adds value by disclosing the verdict taxonomy (allow/review/caution with a reason), the presence of a trust score/tier, identity-changed-hands detection, and that calls are free. It does not discuss rate limits, verdict thresholds, or what happens for unregistered wallets.

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?

Three tight sentences: identity of the registry first, then the return payload, then the usage trigger, closed with the one-word cost signal "Free." Nothing is redundant or buried.

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 takes on the job of explaining returns and does so at the field level (verdict, reason, score, tier, changed hands), which is enough to decide whether to call it. It stops short of describing the exact response shape or behavior on an unknown/unregistered wallet.

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?

There is a single required parameter and schema description coverage is 100% (base58 Solana address with a regex pattern), so the schema already carries full meaning. The description adds no syntax or format detail beyond it; 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?

States a specific verb and resource ("Look up a Solana wallet in SAID Protocol") and enumerates exactly what comes back: registration/verification status, trust score and tier, an allow/review/caution verdict with reason, and identity hand-change. That resource and return profile cleanly separates it from check_token (tokens) and find_agent (agent search).

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 explicit trigger conditions: "Use before sending funds, accepting a job, or trusting a counterparty." It does not name when to skip it or point to a sibling as an alternative, 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.