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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no auth requirements, no rate limits, no indication of what a verdict means or whether screening is cached/auditable. The only behavioral signal is the return type 'XDR1SanctionsVerdict', which hints at an output shape without explaining it.

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?

It is a single terse line with no waste, but this is under-specification masquerading as conciseness. A signature dump is not an appropriately sized description for a screening tool with three parameters and no other documentation.

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 3-parameter tool with no annotations, no output schema, and 0% parameter description coverage, the description is far too thin. The only compensating information is the implied return type, which does not substitute for usage, parameter, or behavioral context.

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 0%, so the description must compensate, but it only restates parameter names with type and required/optional markers ('entity:str!', 'jurisdiction:str?', 'wallet:str?'). It adds no meaning for what a jurisdiction string should look like or how a wallet relates to entity screening.

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 string conveys a specific verb+resource ('screen' against 'sanctions_exact'), so an agent can infer this performs exact-match sanctions screening rather than identity verification or solvency checks. However, it is presented as a raw signature rather than prose, and it never states what the screening actually does or returns in plain terms, so sibling differentiation is left largely to name-similarity guessing.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as verify_id or reconcile. The name implies a sanctions-checking context, but nothing tells the agent when this tool is the right choice over its siblings.

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