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

No annotations are provided, so the description carries the full burden. 'PRO.' implies a paid/subscription tier and the schema's access_token confirms auth is needed, but the description never states this, nor does it cover pagination, result volume, or whether results are exhaustive. A list tool has meaningful behavioral traits left undisclosed.

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 tight sentence with the resource front-loaded and the optional filter second. Only the unexplained 'PRO.' token is wasted.

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 4-parameter, no-output-schema, no-annotation tool, the description covers the core listing concept but omits the 'type' parameter, auth requirements, and any sense of return shape or result limits. Adequate for a simple tool, but with clear gaps.

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 25% (only access_token documented), so the description must compensate. It does explain two parameters implicitly: country (with real-world examples) and since (a date filter), but leaves 'type' completely undefined in both schema and description. Partial compensation warrants a middle score.

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 resource (listings for a country/regime) with concrete examples (Russia, Iran, Belarus). It is distinguishable from the screening siblings (batch_screen, sanctions_check) by being a listing tool, though the description never explicitly contrasts them. The cryptic "PRO." prefix adds no purpose information.

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?

No guidance on when to use this versus sanctions_check or batch_screen, and no prerequisites. The only usage-adjacent note is the optional 'since' filter, which is a parameter behavior, not a when-to-use rule.

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