bea_gdp_by_industry

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

Annotations declare readOnlyHint=true, and the description uses 'Get,' which is consistent with a read operation. The description adds value by detailing the specific tables and industry codes, providing behavioral context beyond the annotation. No contradictions are present.

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 front-loaded with the purpose. Parameter options are listed clearly without unnecessary detail. It is appropriately sized for the tool's complexity.

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 no output schema, the description could explain the response format or pagination. It only states 'Get GDP contribution,' which is somewhat vague. While the parameter details are covered, the lack of output description leaves gaps for an agent to interpret the result structure.

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 description coverage is 100%, so the baseline is 3. The description lists TableID options and industry values, but this information is already present in the schema descriptions. The description adds minimal new semantic value 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 the tool retrieves GDP contribution by industry sector nationally, using a specific verb ('Get') and resource ('GDP by industry'). The tool name and description differentiate it from sibling BEA tools like bea_gdp_by_state and bea_gdp_national by explicitly mentioning 'industry sector' and 'nationally'.

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 parameter options (TableID and industry values) but does not offer guidance on when to use this tool versus alternatives like bea_gdp_national or bea_gdp_by_state. It implies usage through parameter examples but lacks explicit context for tool selection.

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