analyze_taiwan_stock_institutional_flows

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

No annotations are provided, so the description carries full burden. It states it aggregates volumes but does not disclose any behavioral traits like data freshness, limitations, or whether it modifies data. Lacks detail on scope or side effects.

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?

Single sentence is efficient and front-loaded. No wasted words, but could benefit from additional context without becoming verbose.

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 an output schema and 2 parameters, the description is minimal. It does not explain the output structure, data source, or typical use cases. For a tool with no annotations and low schema coverage, the description should provide more context.

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 0%, and the description does not explain the parameters 'stock_id' (format needed) or 'lookback_days' (meaning and valid range). The only hint is 'by investor type', but it does not map to parameters.

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?

Description clearly states the verb 'Aggregate' and the resource 'institutional investor buy, sell and net volumes' grouped by investor type. It distinguishes itself from sibling 'get_taiwan_stock_institutional_flows' which likely provides raw data, indicating a higher-level analysis.

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 explicit guidance on when to use this tool versus alternatives such as 'get_taiwan_stock_institutional_flows' or other analysis tools. The description implies aggregation but does not specify context or exclude other tools.

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