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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds context about what the tool documents (customs-reported vs derived fields) and its data boundary (no commercial quote platform data), which is useful beyond the annotations. It doesn't describe output structure, but an output schema exists.

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 well-structured with Purpose, Guidelines, Limits, and Ex sections. Every sentence earns its place: it explains what the tool does, when to use it, what it excludes, and gives an example. No redundancy with the schema or annotations.

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 documentation tool with one optional parameter, an output schema, and strong annotations, the description is complete. It tells the agent why to call it, what it will learn, and what the tool will not return. Nothing needed for correct invocation is missing.

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 100%, so the schema fully documents the single response_format parameter. The description's example shows usage with response_format='json', which adds a small usage hint, but the baseline of 3 is appropriate since the schema already carries the parameter meaning.

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 purpose: describe the trade flow dataset's source, caliber, unit conversion, derived-field declarations, field table, and compliance boundaries. It clearly distinguishes this tool from siblings like get_trade_flow_summary or query_trade_flows by noting it returns no trade records itself.

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?

Explicitly instructs to call this before running any trade query that will be quoted, and states what it documents. It also names a limit (UN Comtrade official statistics only) and clarifies it returns no trade records, which helps an agent avoid using it as a data source.

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