finnhub_forex_data

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

No annotations provided. The description mentions JSON export for large datasets but does not disclose behavioral traits such as read-only nature, authentication needs, rate limits, or potential side effects from the export parameter.

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 at two sentences with key information front-loaded. However, there is a typo (double period) and the structure could be improved by separating the operations list more cleanly.

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's complexity (9 parameters, no output schema, no annotations), the description is insufficient. It fails to explain parameter usage per operation, return format, or any dependencies, leaving significant gaps for proper tool invocation.

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?

With 67% schema description coverage, the description adds no meaning to parameters beyond what the schema provides. It does not explain how parameters relate to specific operations or provide any additional context.

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 'Access foreign exchange market data' and lists specific operations (get_exchanges, get_symbols, get_rate, get_candles), which distinguishes it from sibling tools focused on other asset classes like crypto or stocks.

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?

The description implies usage for forex data access and lists operations, but does not explicitly state when to use this tool over alternatives or provide exclusions. No guidance on prerequisites or context.

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