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

With no annotations, the description carries the full burden. It does disclose the data provenance and coverage ('11.7K+ PEP records from Wikidata'), which usefully signals that a negative result only means 'not in this dataset'. It says nothing about match semantics, whether the call is read-only, rate limits, or how threshold affects behavior.

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 sentences with the purpose front-loaded and the coverage caveat second. No filler, no restatement of the tool name.

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?

This is a screening tool with no output schema and no annotations, so the description needs to say what a result looks like (boolean, match score, candidate list) and what a miss implies. It only hints at dataset scope and never describes the return value, leaving a real gap for callers.

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%, so both 'query' and 'threshold' (including the 0.82 default) are already documented in the schema. The description adds no extra meaning such as name-format expectations or how lowering the threshold changes results, 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?

States a specific verb ('Check') plus the exact resource ('Politically Exposed Person (PEP)') and even names the backing data source. 'PEP' versus the sibling names check_sanctions and check_entity is enough for an agent to route correctly without opening a schema.

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 or when-not-to-use guidance, and no mention of the obvious alternatives (check_sanctions for sanctions lists, check_entity for general lookups). The agent must infer that PEP screening is a distinct check from sanctions screening.

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