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

Annotations already cover read-only, idempotent, non-destructive, open-world, so the safety profile is free. The description adds genuinely useful context beyond that: the verdict categories returned, the underlying signals, the sybil-manufactured-ratings interpretation, and the $0.02 cost — cost is a real behavioral trait annotations cannot express.

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-loaded with the core question and the verdict vocabulary, then evidence, then the sybil rationale, then access details. Dense and mostly waste-free, though the 'Most Base ERC-8004 reviewer activity shows coordinated sybil behavior' line leans promotional and repeats the manufactured-ratings point.

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 return-value explanation isn't strictly needed, yet the description still pre-frames the verdict enum and evidence metrics. With only two simple parameters and full annotation coverage, the only missing piece is the identifier exclusivity/requiredness rule.

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 0%, so the description must carry the load, and it does define both parameters: agent_id as an ERC-8004 agent id and solana_asset as a Solana 8004 agent pubkey, framed as an 'alternative'. It doesn't spell out that exactly one is required (both schema fields are optional with default 0/""), which is the remaining gap.

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?

Names a specific verb-like question (is reputation earned or bought) and the concrete output vocabulary (ORGANIC / BURST / FARM / MIXED / NONE) plus the evidence fields. It also explicitly positions itself against the sibling should_i_pay, so an agent can pick it 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?

States the triggering context clearly: it is 'the follow-up to should_i_pay that explains WHY a verdict is CAUTION', which tells the agent the sequencing and the alternative. It stops short of stating when not to use it (e.g. before any should_i_pay verdict exists) or that at least one identifier is required.

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