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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the external-call and write profile is partly covered. The description adds a failure-mode note ('a missing key writes nothing and does not pass the file'), which is useful but phrased too ambiguously to be actionable.

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?

Very short and front-loaded, but two of the four sentences ('Same as Screen OpenSanctions', the missing-key clause) are redundant or unclear rather than informative.

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 and readOnlyHint=false imply the tool persists a screening result to the case, yet the description never says what is recorded or returned. Combined with partial parameter documentation, an agent cannot fully anticipate the effect of a call.

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 only 33% schema coverage, the description should compensate more; it names the screening subject (name) and the SANCTIONS/PEP check type, but says nothing about caseId semantics, whether name is optional or where it is sourced, or default checkType behavior.

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?

Specific verb+resource: screens a name against OpenSanctions for SANCTIONS or PEP checks. The phrase 'Same as Screen OpenSanctions' is redundant filler rather than sibling differentiation, but the core action 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?

No guidance on when to screen versus when to use related siblings like resolve_listed_company or read_listed_company, and no prerequisites (e.g., API key requirement, case state) are stated beyond a cryptic hint.

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