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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context beyond that: the sources screened (three sanctions regimes plus adverse media), the output shape (a detailed risk verdict per company), and the cost ($0.05 each) which matters for invocation budgeting. It does not cover auth, rate limits, or latency, so it stops short of a 5.

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 first sentence is repeated verbatim, wasting a full sentence in a four-sentence description and making the definition look copy-pasted. The remaining content is front-loaded and short, but the duplication directly violates the 'every sentence earns its place' test.

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?

Output is summarized (detailed risk verdict per company) and cost is stated, which compensates for the absent output schema. However, the input side is opaque: with 0 required parameters and only a nested 'input' object described by a URL, the description never clarifies what the caller must actually supply to screen a company.

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%, and the single nested 'input' object is documented by the schema itself pointing to the Apify page. The description adds nothing about what identifiers or fields should go into that input, so the baseline 3 applies.

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?

Names a specific verb (screen) and resource (companies) plus the exact scope: EU, OFAC and UK sanctions lists + adverse media. That scope separates it from generic siblings like company_due_diligence or nordic_company_registry, though it never names a sibling explicitly. The purpose is genuinely clear despite the duplicated sentence.

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?

There is no when-to-use guidance, no prerequisites, and no mention of when another tool (e.g. company_due_diligence, b2b_competitor_monitor) would be preferable. The description only describes what the tool is, leaving the agent to infer the selection context.

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