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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower, yet the description adds real operational context: the verdict taxonomy (blocked/review/clear), the $0.03 x402 pricing, the x-credit-token prepaid header, the 1 free call/day, and that no API key is needed. That is meaningful disclosure beyond the annotations.

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?

The core value proposition is front-loaded in the first sentence, followed by the audience and then payment mechanics. It is well ordered and reasonably tight, with only mild redundancy in the pricing sentence.

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 values need not be explained, and the description still names the possible verdicts. Pricing, auth, and required input are all covered; only explicit sibling routing is missing for a tool sitting among many screening alternatives.

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?

With a single parameter at 100% schema coverage, the schema already documents "address." The description only restates "Required input: address" without adding format, chain, or checksum expectations, so it earns the baseline 3 rather than more.

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 states a specific verb and resource: combined counterparty screening of an address that fuses OFAC sanctions matching, EOA/contract profiling, and contract risk flags into one verdict. An agent understands the aggregation scope, though it never names which sibling (e.g. sanctions, counterparty_check) it supersedes.

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?

"Built for compliance agents" and "counterparty screening for an address" imply the use context, but there is no explicit when-to-use/when-not guidance and no routing against the many overlapping siblings like sanctions or address_trust. Usage is inferable rather than stated.

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