query_trade

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

No annotations are provided, so the description carries the full burden. 'Query' implies a read-only operation, and the dataset size is noted, but there is no disclosure of return format, pagination, safety profile, or behavior differences between query types. This is insufficient for a tool with 9 distinct operations.

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?

Two concise sentences with no filler. The first sentence states the action and dataset, the second lists supported query types. Every word contributes to understanding the tool's purpose.

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?

Despite 9 query types and 8 parameters, the description only lists the query types without explaining each one's intended use or output. No output schema exists, so an agent cannot predict what 'balance' or 'heatmap' returns. This is a significant completeness gap for a complex 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 descriptions for all parameters, so the baseline is 3. The description adds minor context about HS2-CN8 codes and the 27 EU countries, but does not substantially enhance parameter understanding beyond the schema.

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 queries EU trade data from Eurostat COMEXT, names the dataset, and enumerates the supported query types. The scope (27 EU countries, HS2-CN8 codes) makes it specific, but it does not explicitly distinguish itself from sibling tools like query_customs.

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 EU trade data queries but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives or exclusions, leaving selection to the agent's inference from the context.

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