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

Annotations already declare readOnlyHint=true and destructiveHint=false, lowering the behavioral disclosure burden. The description adds meaningful context: exact data sources (OFAC, BIS, State), the fused verdict output with flags, JSON format, and a $0.20 USDC price. No contradictions with annotations.

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 one dense, information-rich sentence with no filler. It slightly repeats the title and bundles price alongside 'premium call', so it is efficient but not maximally tight.

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 tool with no output schema and complex bundled behavior, the description covers the input (name, commodity), the action (screening + Federal Register), the output (verdict with flags, JSON), and price. The optional agency parameter is left to the schema, which is acceptable given full schema coverage.

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 covers all three parameters with descriptions (100% coverage), so the description need not repeat them. It mentions 'counterparty name' and 'commodity/topic' in context, but adds no syntax or format detail beyond the schema.

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 action ('screens a counterparty name') against a named resource (US Consolidated Screening List) and adds a second action (pulls Federal Register actions). This distinguishes it from siblings like legal_sanctions_screen or legal_reg_watch, which likely cover only one of these areas.

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?

It clearly frames the tool as 'for import/export compliance' and as a 'bundle' combining two data sources. However, it does not explicitly name alternative tools or exclusion criteria (e.g., when to prefer simple sanctions screening over this premium bundle).

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