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

With no annotations, the description carries the full burden and does disclose the payment mechanism ($0.01 USDC/call, x402, eip155:8453), fuzzy matching with alias handling, and the returned fields — context the schema cannot convey. It is silent on no-match behavior, result truncation/pagination, and what a paid call failure looks like, which matters for a paid mutation-adjacent tool.

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, front-loaded with the paid-access metadata before the capability statement. The bracketed payment prefix is slightly cluttered but carries decision-relevant information rather than 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?

Seven parameters with no output schema, yet the description names the return fields (score, list, programs, countries), covering the biggest gap. Remaining gaps are minor: nothing about empty-result handling or result caps, though max_results in the schema partly covers the latter.

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 100%, so the baseline is 3. The description reinforces the multi-list and fuzzy/alias semantics but adds no syntax or format detail beyond what the schema already documents for name, lists, country, threshold, and the boosting fields.

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: screen a person or company name against OFAC SDN, UN, EU and UK sanctions lists. The phrase 'person or company name' implicitly distinguishes it from the sibling sanctions_crypto_address, though it never names that sibling explicitly.

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?

No explicit when-to-use or when-not guidance and no named alternative. The 'one call' phrasing and the list coverage imply this replaces four single-list lookups, and the cost prefix hints it is a paid endpoint, but the agent must infer all of that.

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