bea_multinational_enterprises

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds useful contextual constraints (e.g., State and Parent are AMNE-only, and AMNE stats require ownership_level and non_bank_affiliates_only), but it does not describe the response structure, pagination, or any other behavioral traits. It adds some value but not extensive behavioral disclosure.

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 compact and well-structured, using bullet-like lines to present required parameters and conditional settings. Every sentence contributes useful guidance without redundancy, fitting within a small block.

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 the core directions, classification, and AMNE-specific parameters, but it omits that 'year' is a required parameter (as shown in the schema) and does not explain how to use state, country, industry, or series_id filters. For a tool with 9 parameters, this leaves notable gaps, though the schema helps compensate.

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%, giving a baseline of 3. The description adds meaning beyond the schema by explaining the semantics of DirectionOfInvestment values (e.g., 'Outward' = U.S. investment abroad / foreign affiliates) and clarifying when ownership_level and non_bank_affiliates_only are needed. This is meaningful added value.

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 identifies the tool as retrieving Direct Investment (DI) and Activities of Multinational Enterprises (AMNE) data, with explicit subcategories (Outward, Inward, State, Parent). This specific resource focus distinguishes it from sibling BEA tools like bea_gdp_national or bea_international_transactions.

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 gives clear instructions on which direction/classification to use and when additional AMNE parameters are necessary, but it does not mention when to prefer this tool over related BEA options or explicitly state exclusions. It provides in-tool usage context but lacks tool-selection guidance.

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