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

With no annotations, the description discloses the paid nature ($0.25), payment-first ordering, and output range. It also names data sources and risk flags. It does not cover failure modes or output structure, but core behavioral context is present.

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 tight sentences; the most important fact (PAID $0.25) is front-loaded and every clause adds information. No filler.

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?

Covers cost, order, and result range, but leaves ambiguity around payment_tx (optional in schema yet described as required, format unclear) and does not describe the result structure beyond the numeric score. For a paid tool with no output schema, a bit more detail would help.

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?

Target is described in the schema as '0x address'; the description adds that it is a wallet/agent. Payment_tx is mentioned but not described beyond being the payment transaction to pass after paying. With 50% schema coverage, the description partially compensates but leaves the format of payment_tx unspecified.

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 output (trust score 0-100) and resource (any Base wallet/agent), with data sources (witness ledger, risk flags, seal). It does not use an explicit verb like 'returns' and doesn't contrast with siblings, but the intent is unambiguous.

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?

Provides a clear operational sequence ('Pay first, then pass payment_tx + target') but no guidance on when to prefer this over sibling tools or exclusions. Usage context is implied by the paid trust-score purpose rather than explicit.

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