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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety profile is covered. The description adds one genuinely useful behavioral note: results are screening leads requiring review rather than confirmed determinations. It says nothing about the meaning of the score, default thresholds, or the volume/format of returned candidates.

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 short sentences, zero filler, with the core operation front-loaded and the important caveat placed immediately after. Nothing is redundant or buried.

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?

With no output schema, 0% parameter coverage, and an unexplained relevance threshold, the description leaves too much unspecified for correct invocation. An agent cannot tell what a returned match looks like, what score scale applies, or how to tune min_score for looser or stricter screening.

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% for both parameters, so the description must compensate and does not. It never explains the expected format of 'name' (full name, order, aliases) nor the meaning, default, or effect of 'min_score' despite its 0.5–1.0 range, leaving the agent to guess how threshold changes affect results.

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 (screen) and a specific resource (a name against the OFAC SDN list and aliases), so the operation is unambiguous. It does not differentiate from any sibling tool, though the sibling list contains no obvious sanctions alternative, so the gap is mild.

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 description implies usage for sanctions/adverse-media style checks and adds an interpretive caveat that a match is a lead for review, not a determination. It gives no explicit when-to-use or when-not-to-use conditions, and no prerequisite or follow-up guidance (e.g., which tool to use after a hit).

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