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

With no annotations, the description does real work: it discloses the return vocabulary (match / possible_match / no_match with register links), the free-tier throttle (3 checks per hour) and the paid model (10 credits / $0.10 with an x-api-key). It does not say what happens when the hourly limit is exceeded or whether failed lookups still consume credits, which keeps it short of full disclosure for a zero-annotation tool.

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?

Four sentences, each carrying a distinct fact: what is screened, what comes back, what it costs, and what the ignored parameter does. The highest-value information (the registers and the verdict vocabulary) is front-loaded with zero filler.

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?

There is no output schema, and the description compensates by naming the three possible verdicts and the linked register entry behind each hit. Combined with cost, quota and the inert-country caveat, an agent has everything needed to decide whether and how to call it.

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 `name` and `country` are already documented, including the note that country is not yet applied as a filter. The description repeats that caveat but adds no new meaning to either parameter, so 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 and resource ('Check one organization') and enumerates the exact registers screened (OFAC SDN, UK OFSI, UN Security Council, World Bank debarment). This is unmistakably distinct from siblings like check_balance, new_uk_companies and search_contracts without opening any 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?

The scoping phrase 'one organization' tells the agent this is single-entity screening, not a list search, and the pricing/quota lines establish the practical cost of calling it. There is no explicit when-not guidance or named alternative, but no sibling offers an equivalent screen, so the gap is small.

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