list_all_icb_industries

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

With no annotations provided, the description carries full burden. It mentions output format options and return type but does not disclose behavioral traits like data freshness, rate limits, or safety (e.g., read-only). This is insufficient for an agent to understand the tool's behavior.

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, using a single sentence for purpose followed by a docstring-style parameter explanation. It is front-loaded and efficiently communicates the key details 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?

For a simple listing tool with one parameter and no output schema, the description covers purpose and parameter semantics adequately. However, it lacks usage guidance and behavioral context, which are important for an agent to use it correctly among many sibling tools.

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 description explains the single parameter 'output_format' with its options and default, adding that 'toon' is optimized for AI. This provides semantic meaning beyond the schema, which only lists the enum without explanation. Schema coverage is 0%, so the description compensates well.

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 'List all ICB industries from stock market', specifying the verb 'list' and the resource 'ICB industries'. This distinguishes it from sibling tools like 'get_all_symbols_by_industry' which focus on symbols within industries.

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_all_symbols_by_industry' or 'list_all_companies_with_details'. The description lacks context for selecting this tool over others.

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