get_industry_detail

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

No annotations are provided, so the description carries the full burden. It states what data is returned ('child industries and data availability') but does not disclose rate limits, authentication, or explicitly confirm read-only behavior. The 'Get' verb implies a read operation, but behavioral context beyond the output content is limited.

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 concise segments: purpose and parameter note, with no filler. It front-loads the primary action and resource, then gives the essential parameter detail.

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 one-parameter tool with an output schema, the description covers purpose, usage context, and parameter semantics. The output schema presumably documents the return structure, so the description is complete without over-explaining.

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 0%, and the description fully compensates: 'naics is the NAICS code (e.g. '5112' for Software Publishers)' adds type, format, and a concrete example, making the parameter meaningful beyond the bare schema entry.

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 uses a specific verb ('Get') and resource ('detailed information for a single BLS industry') with scope ('including child industries and data availability'). It clearly distinguishes from search_industries by emphasizing 'single' and 'drill into,' but does not explicitly differentiate from industry-specific siblings like get_industry_employment.

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?

Provides clear usage context: 'Use this after search_industries to drill into a specific industry.' This establishes a workflow and implies when to use the tool, but does not mention exclusions or alternatives beyond search_industries.

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