finnhub_stock_fundamentals

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

With no annotations, the description carries full burden for behavioral disclosure. It mentions JSON export support but fails to state read-only nature, authentication needs, rate limits, or any side effects. The operations imply read access but are not explicitly described as non-destructive.

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 short and front-loaded with purpose. However, it includes a typo (double period) and the operation list duplicates schema information, slightly reducing efficiency.

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?

For a tool with 8 parameters, one required, and no output schema, the description is incomplete. It lacks explanations for when to use each operation, data range implications, frequency options, and metricType meaning. Significant gaps remain for proper agent usage.

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 coverage is 63%, but the description adds little beyond the schema. It does not explain uncovered parameters like freq, operation, or metricType. The list of operations provides some context but no semantic meaning for individual 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?

The description clearly states the tool accesses fundamental financial data including metrics, dividends, and revenue breakdown. It provides a specific verb 'Access' and resource 'fundamental financial data', but does not differentiate from sibling tools like finnhub_stock_market_data or finnhub_stock_ownership.

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 is provided on when to use this tool versus alternatives or which operation to choose. The description lists operations but offers no context for selection, leaving the agent without decision criteria.

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