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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses significant behavior: daily list refresh, ranked-candidate output that is not a determination, and the paid x402/USDC pricing model on Base. Cost and payment mechanics are exactly the kind of operational context an agent needs and cannot get from annotations alone.

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, front-loaded sentences pack purpose, mechanism, output semantics, and price without redundancy. The pricing clause is slightly grafted on but still earns its place for an x402-paid tool.

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?

No output schema exists, and the description usefully characterizes the return value as ranked candidates for review. However, with 6 parameters at 0% schema coverage, the definition is incomplete on input semantics, which an agent needs before calling.

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% across 6 parameters, so the description carries the full explanatory burden. It only indirectly implies the 'kind' (person/company) and 'lists' parameters; dob, limit, and nationality are not addressed at all, leaving half the parameters undocumented in both schema and description.

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 ('Sanctions screening candidates for Korean and North Korean names') and details the mechanism (romanisation expansion plus matching against OFAC/UN/EU/UK lists). This clearly distinguishes it from siblings like kr_name_romanize, which only transliterates, and kr_entity_resolve.

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?

The context is implied — screening Korean/NK names against official sanctions lists — but there is no explicit when-to-use/when-not guidance and no named alternative such as kr_name_romanize or kr_entity_resolve. The note that it returns candidates for human review rather than a determination is a useful usage qualifier.

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