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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that it is a pure reference lookup returning classification details, controlled jurisdictions, and license requirements, which clarifies determinism and scope. It does not disclose error behavior for unknown or malformed ECCNs.

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?

Purpose is front-loaded in the first sentence, followed by return scope and examples. The ECCN background paragraph and three examples are somewhat verbose for a one-parameter lookup, but each line is informative and scannable.

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 simple read-only lookup with an output schema, the description supplies enough context: what an ECCN is, what the call returns, and representative inputs. The main gap is the absence of any pointer to sibling tools for related tasks (screening, HS classification).

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% and the single parameter is fully described, including case-insensitivity, so the schema does the heavy lifting. The description's example codes reinforce but do not extend the schema's meaning beyond it.

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 verb (look up) and resource (ECCN) and defines what an ECCN is, so an agent understands the domain immediately. However, it never distinguishes itself from close siblings like hs_code_lookup, goods_classify, country_export_controls, or export_controls_screen, so sibling routing is left to inference.

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?

"Pure reference tool" implies this is a static lookup rather than a screening action, which is weak implicit guidance against using export_controls_screen or sanctions_screen. There is no explicit when-to-use/when-not-to-use statement or named alternative, so usage must be inferred from the domain framing.

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