ita_trade_events

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

The readOnlyHint annotation already declares this a safe read operation, and the description's verbs ('search', 'find') are consistent with that. It adds the behavioral detail that events are 'upcoming' but does not disclose pagination, sorting, or output structure, leaving some room for improvement.

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 two sentences with no filler: the first states the resource and scope, the second gives search criteria and purpose. It is front-loaded and every clause earns its place.

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 read-only search tool with three optional parameters and no output schema, the description covers the essential aspects: what is searched, how to filter, and the intended benefit. It could mention what the results contain, but the current level is adequate for a simple search operation.

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?

All three parameters (limit, query, country) are fully described in the schema with 100% coverage, so the description adds little beyond confirming keyword and country as search dimensions. The phrase 'by keyword or country' maps to query and country but does not enhance syntax or format details.

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 the tool searches international trade events, specifying types (trade shows, missions, seminars) and the main filter dimensions (keyword, country). It also names the target audience (U.S. businesses), making its purpose distinct from unrelated siblings like ita_tariff_rates.

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 the use case—finding upcoming trade events by keyword or country—but does not explicitly mention when to use this tool over alternatives. There are no exclusions or comparisons to other trade-related tools, so guidance is only implicit.

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