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

Annotations already include readOnlyHint=true, openWorldHint=true, and idempotentHint=true. The description adds value by specifying data sources ('EU dual-use export control lists and ICAO/IMO restricted items data') and output details ('risk levels, applicable regulations, and source references for audit trails'). It does not contradict any annotation.

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 three sentences, front-loaded with the user role and purpose. Each sentence adds essential context: what the tool does, what input to provide, and what output to expect. There is no fluff or repetition of schema fields.

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 tool has an output schema, so return values are already specified. The description covers the tool's purpose, input format, and output highlights, which is sufficient for a moderately complex analysis tool. Minor gaps like rate limits or edge cases are not critical given the annotations and output schema.

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 only 33%, so the description must compensate. It explains the main input (bomItems) by saying 'Input a list of part numbers, descriptions, or HS codes', which maps to partNumber, description, and hsCode fields. However, it does not mention the 'quantity' field or the 'async' and 'includeSources' parameters, leaving gaps that the schema's sparse descriptions only partially fill.

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 it 'analyzes bills of materials (BOMs) against EU dual-use export control lists and ICAO/IMO restricted items data' to 'assess export compliance risks.' This is a specific verb+resource combination that distinguishes it from sibling tools like dual_use_tech_diversion_monitor.

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?

Provides clear context: 'As a COO, quickly assess export compliance risks for components in your supply chain.' This indicates the intended user and scenario. It does not explicitly mention when not to use it or alternative tools, but the context is unambiguous enough for selection.

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