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

With no annotations, the description carries the full behavioral burden, but it only says 'PRO' and names filters. It does not disclose pagination, default behavior when no filters are supplied, authentication needs beyond the schema token note, or what the response contains.

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 single tightly packed sentence with the key filters front-loaded and no redundant material. Its terseness creates completeness gaps elsewhere, but as a conciseness matter there is no waste.

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 four-parameter list endpoint with no annotations and no output schema, the description is too thin. It omits return format, default limit behavior, what happens with no regime or since filter, and how the premium 'PRO' gating works.

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%: since and access_token are documented in the schema, while regime and limit are undocumented there. The description adds useful regime examples and clarifies that since means 'designated since a date,' but it does not explain limit at all.

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 clearly states that the tool returns designations filtered by regime and/or designation date, with examples like Russia and Iran. It does not explicitly distinguish itself from sibling screening/check tools, but the resource and filters are clear.

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 guidance on when to use this tool versus siblings such as sanctions_check or entity_detail, nor any prerequisites or exclusion conditions. The 'and/or' phrasing implies optional filters but does not explain usage context.

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