bea_multinational_enterprises

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

Annotations indicate readOnlyHint=true, so the tool is read-only. The description adds valuable behavioral context about parameter dependencies (e.g., ownership_level and non_bank_affiliates_only required for AMNE stats) and explains the meaning of each direction and classification value. No contradictions.

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 well-structured with bullet points and clear parameter explanations. It is front-loaded with the core purpose. At ~150 words, it is reasonably concise, though some parameter details could be trimmed.

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 tool has 9 parameters and no output schema, the description covers key concepts (direction, classification, AMNE-specific params) but lacks examples or guidance on combining parameters. It references bea_dataset_info for series IDs, which helps. Overall adequate for a moderately 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?

The input schema already has 100% parameter descriptions, but the description adds significant value by explaining the allowed values for direction_of_investment and classification, and clarifying when ownership_level and non_bank_affiliates_only are needed. This goes beyond the schema's basic 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 starts with a clear verb and resource: 'Get data on Direct Investment (DI) and Activities of Multinational Enterprises (AMNE).' It is distinct from sibling tools like bea_gdp_by_industry or bea_fixed_assets, which focus on other economic data. The parameter list further clarifies the scope.

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 does not explicitly state when to use this tool versus alternative BEA datasets. It provides parameter guidance (e.g., ownership_level required for AMNE stats), but no direct comparison or exclusion criteria for sibling tools. Usage context is implied.

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