getForeignCategoryHoldings

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

No annotations are provided, and the description merely states 'Get' without disclosing behavior like return format, data scope (e.g., all categories or filtered), or whether results are aggregated. The burden is on the description, which fails to inform.

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 a single sentence with no wasted words, but it is too brief and omits critical information, making it inadequate rather than efficiently concise.

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 no parameters and no output schema, the description should clarify what data is returned (e.g., all industry categories, current holdings). It fails to provide essential context, leaving the agent to guess.

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 schema has zero parameters, but the description mentions 'by industry category,' suggesting a missing filtering parameter. This mismatch undermines clarity. Schema coverage is 100% only because there are no parameters to describe, so the description adds negative 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 states 'Get foreign investor holdings by industry category,' which is a clear verb and resource, but it implies a parameter (industry category) that does not exist in the input schema, causing confusion. It distinguishes from siblings like 'getTopForeignHoldings' only vaguely.

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 on when to use this tool versus alternatives such as 'getTopForeignHoldings' or 'getIndustryEPS'. The description provides no context about prerequisites or typical use cases.

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