Loading ToolBench
Macro-event and sector impact intelligence for Indian financial markets. Structured analysis of how policy, economic, weather, and geopolitical events affect Indian market sectors.
Single tool with critical definition gaps. The analyze_news tool has a reasonable name and description, but lacks comprehensive parameter documentation, no output schema definition, and missing error handling guidance. The description (103 chars) meets minimum length but is generic and doesn't explain WHEN to use this tool vs alternatives, what sector_vector structure contains, or what errors may occur. Parameters lack any description text beyond type declarations. No input validation, no structured output schema documented, no error recovery guidance.
Analyze one Indian financial headline with Indian Market Intelligence for Macro Event & Sector Impact Analysis and return sector_vector for sector impact analysis. Requires API key configuration.
Parameters lack descriptions. 'published_at' is documented only as a type, not explaining what format is expected (ISO 8601? Unix timestamp?), when it should be provided, or what happens if omitted.
Output schema not documented. Tool description mentions 'sector_vector for sector impact analysis' but does not specify the structure of this object: is it a dict of sector names to impact scores? What fields does it contain? What are valid value ranges? LLM cannot plan downstream usage without this.
No error handling or recovery guidance. Tool description does not explain what happens if API key is missing, if the API is unreachable, if the headline is malformed, or if quota is exceeded. LLM receives no actionable error information.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 46 | 2026-07-28+ | v2 |
Tool description is generic and context-poor. Does not explain WHEN to call this tool (what user intents trigger it?), what 'Macro Event & Sector Impact Analysis' means in operational terms, or how the results should be used. At 103 characters, it wastes tokens on the product name repetition rather than explaining utility.
API key dependency not handled safely. Tool requires AION_API_KEY environment variable but does not document this in parameter constraints or return actionable error if missing. Agents cannot know whether to retry or ask user to configure.
No input validation described. Headline parameter has no length constraints, encoding requirements, or language specification documented. Invalid inputs will fail silently or at the API, with no recovery path for the LLM.
Published_at parameter is optional but its purpose and format are unexplained. Does the API timestamp the analysis if this is omitted? Does it affect sector vector calculation? When should an agent include it?