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

Annotations already declare read-only and idempotent behavior, but the description adds key context: full data requires a $0.25 USDC payment via x402 on Base, and mentions the API endpoint. This goes beyond annotations by disclosing a paywall constraint and delivery mechanism, which is valuable behavioral information.

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 two sentences, directly front-loaded with the tool's core function, then followed by specific details on outputs and payment. Every sentence adds informational value with no redundancy or filler.

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?

The description explains what the tool returns (crosscheck status for four lists plus jurisdiction count) and flags the payment requirement for full data. The output schema exists, but the description still provides a concise preview of the response structure, making it fairly complete for a relatively simple one-parameter tool.

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 100% with a single 'commodity' parameter that has a clear enum and description. The description adds context about the 20 commodities and the crosscheck nature, but does not elaborate on parameter syntax or usage details beyond what the schema already provides, so a baseline of 3 is appropriate.

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 the tool's function: multi-jurisdiction critical mineral classification across specific lists (US DoD, EU CRMA, IEA, Japan METI). It uses a specific verb ('returns crosscheck status') and resource ('20 commodities'), distinguishing it from sibling tools like china_trade_control or supply_resilience.

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 implies usage for cross-checking critical mineral classifications across multiple jurisdictions and commodities, but does not explicitly state when to prefer this tool over alternatives. No exclusions or comparisons to sibling tools are provided, leaving usage context somewhat implied rather than explicit.

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