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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context not in the annotations - the shape of the return payload (aliases, listing regulation, identifying details) and the `stale` freshness flag, which is important because there is no output schema. It remains silent on match behavior (fuzzy vs exact), result ordering and what the freshness window actually is.

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 sentences, front-loaded with the dataset scope, then the return contract. No filler or restated title, and both sentences carry information an agent needs.

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, the description correctly takes on the return-value burden by naming the fields returned and the `stale` flag. For a three-parameter search tool with annotations covering safety, the only meaningful gaps are matching semantics and result ordering/pagination.

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 coverage is 67%, with query and subject_type documented and only `limit` undocumented (its default/min/max make it self-evident). The description's 'by name or alias' largely restates the schema and oddly omits the exact-ID-number capability the schema advertises, so it adds little meaning beyond the structured fields - baseline 3.

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 ('Search') and a precisely scoped resource ('EU consolidated financial sanctions list (persons and enterprises)'), and the EU jurisdiction implicitly separates it from ofac_sanctions__search, uk_sanctions__search and un_sanctions__search. It never names or contrasts a sibling explicitly, so it stops short of a 5.

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?

Usage is only implied: an agent can infer this is the tool for finding listed parties by name/alias, and the schema hints that exact ID numbers also work. There is no explicit when-to-use vs when-not guidance, no mention of preferring a lookup-style sibling for known identifiers, and no guidance on narrowing with subject_type.

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