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

No annotations are provided, so the description carries the load. It discloses what is returned ('Full record' with named fields) and implies premium/subscriber access via 'PRO.', but says nothing about authorization requirements (the access_token param implies them), error behavior, or rate limits. Adds partial value but leaves meaningful behavioral gaps.

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?

A single sentence plus a tier marker; nothing redundant, and the key information (full record, field list, ID source) is front-loaded. Slightly cryptic abbreviations ('PRO.') prevent a 5.

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 names the return fields, and it identifies the ID namespace. However, for a lookup tool sitting among many overlapping screening siblings, the absence of routing guidance leaves the definition only minimally complete.

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 50% because 'id' has no schema description, but the description compensates by explaining it is a 'UK Sanctions List unique ID' — meaningful semantics an agent couldn't get from the bare string type. The access_token param is documented in the schema itself.

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/resource combination: returns the full record for a UK Sanctions List unique ID, and enumerates the fields included (aliases, regime, designation date, DOB, nationality). It does not distinguish itself from siblings like global_entity_detail or sanctions_check, so an agent must infer which lookup applies.

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?

Only guidance is the terse 'PRO.' marker, which hints at a subscription tier but doesn't say when to use this versus sanctions_check (screening) or global_entity_detail (non-UK lists). No exclusions or prerequisites are stated.

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