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

Annotations already declare readOnlyHint and idempotentHint, but the description adds meaningful behavioral context: it discloses the tool's dependence on mirror freshness and readiness, and states that screening cannot run on a not-ready mirror. It also reveals the data provenance (URLs and licenses), which is not covered by annotations. No contradiction with annotations, but the freshness caveat is the main added behavioral insight.

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 description is a compact two-sentence block (plus an attribution sentence) with zero fluff. The purpose is front-loaded in the first sentence, usage guidance in the second, and licensing attribution appended at the end. Every sentence earns its place, and the structure leads with the most critical information.

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?

For a parameterless tool with an output schema and read-only/idempotent annotations, the description fully covers what an agent needs: it lists the data sources, the fields returned, the readiness/freshness caveat, and licensing. The output schema handles return format details, so the description is complete for safe and correct invocation.

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?

The tool accepts no parameters (input schema is empty), so there are no parameter semantics to explain. Per the rubric, a baseline of 4 is appropriate; the description correctly omits parameter details because none exist. Nothing more could be added.

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?

The description states a specific verb (list) and resource (sanctions watchlists and GLEIF datasets), enumerates the exact datasets (OFAC SDN + Consolidated, EU, UK, UN) and the fields returned (record count, source URL, license, readiness, as-of timestamp). It clearly distinguishes itself from sibling tools that perform entity lookups, screening, or tracing, leaving no ambiguity about its purpose.

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 description explicitly directs agents to use this tool 'for provenance and freshness on any result' and explains the practical implication that 'results are only as current as the last mirror refresh' and 'a not-ready mirror means screening cannot run yet.' This gives clear when-to-use context and implies this should be checked before relying on screening results, while implicitly contrasting with the operational sibling tools.

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