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

Annotations already carry the read-only and idempotent profile, so the bar is lower. The description adds meaningful behavioral scope beyond that: 'yearly' reveals the data frequency and 'global' signals that this returns world-level aggregates rather than country-specific breakdowns. No contradiction with annotations 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?

A single, front-loaded sentence with zero filler. It states the action, the data scope, and the key input constraint (HS levels) efficiently without repeating schema details.

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?

Given the read-only, idempotent annotations and the presence of an output schema, the description is sufficiently complete for an agent to select and invoke the tool. Minor ambiguity remains about whether 'global' means a single world total or a breakdown by partner, but the output schema and sibling context likely cover this.

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 baseline is 3. The description only alludes to hs_code ('HS2, HS4, or HS6 product') and provides no additional semantics for year, limit, or offset that the schema does not already state. It does not compensate beyond the schema's full parameter documentation.

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 verb ('Return') and a clear resource: reported yearly global merchandise flows and growth for an HS2, HS4, or HS6 product. It naturally differentiates from siblings like get_country_trade or get_corridor_trade by emphasizing product-level and global scope, though it does not explicitly name a sibling.

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?

No guidance is given about when to use this tool versus alternatives such as get_global_trade or get_country_trade. The purpose implies the tool is for product-level data, but the description does not articulate selection conditions, exclusions, or scenarios where another sibling would be preferable.

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