finnhub_stock_market_data

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

With no annotations provided, the description only mentions JSON export support but lacks details on rate limits, data freshness, authentication needs, or side effects of operations.

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 brief (two sentences plus a list) and front-loads the purpose, but the list of operations is placed without clear separation, slightly reducing readability.

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 11 parameters and 7 operations, no output schema, and no annotations, the description is insufficient. It does not explain parameter dependencies, operation-specific behaviors, or return value structure.

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 high (73%), so the baseline is 3. The description adds minimal new meaning beyond the schema, only indicating that JSON export is supported for large datasets.

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 stock market data' with specific examples (real-time quotes, historical candles, etc.) and lists all operations, effectively distinguishing it from sibling tools like finnhub_crypto_data or finnhub_forex_data.

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; no mention of prerequisites or scenarios. The description simply lists operations without explaining which to choose.

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