bea_intl_services_trade

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

Annotations declare readOnlyHint=true, so the tool is read-only. The description adds the behavioral constraint on parameter combinations, but does not discuss error handling, rate limits, or data freshness. With annotations covering safety, a score of 3 is appropriate.

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 concise and well-structured: a one-sentence purpose, followed by a clear note, then bullet-like lists of values. Every sentence adds value without redundancy.

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 description covers input parameters well but lacks information about the return format or data structure, especially given no output schema. For a complex data retrieval tool, this is a gap, though the cross-reference to bea_dataset_info helps.

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%, but the description adds meaning by providing valid value examples for TypeOfService, TradeDirection, and Affiliation, and the critical interplay constraint between TypeOfService and AreaOrCountry, which is not captured in individual schema descriptions.

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 'Get U.S. international trade in services data (annual)' with a specific verb and resource. It does not explicitly distinguish from siblings like bea_international_transactions, but the name and context make the purpose clear.

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 provides a crucial constraint: 'BEA requires either a specific TypeOfService or a specific AreaOrCountry. You cannot use All for both simultaneously.' It also references bea_dataset_info for discovering values. However, it does not compare with alternative tools.

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