Financial Modeling Prep MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'provides key statistics' but does not specify what data format is returned (e.g., JSON structure, numerical values), whether it's real-time or historical, any rate limits, authentication requirements, or error conditions. For a data-fetching tool with zero annotation coverage, this leaves significant behavioral gaps.

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 efficiently structured in two sentences: the first states the tool's purpose and API context, the second elaborates on the statistics provided. It is front-loaded with the core function ('Analyze insider trading activity') and avoids redundant phrasing. However, it could be slightly more concise by integrating the two sentences more tightly.

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 (fetching financial statistics), lack of annotations, and no output schema, the description is incomplete. It does not explain the return format, data recency, potential limitations (e.g., time periods covered), or how to interpret the statistics. For a tool with one parameter but significant output implications, more contextual detail is needed to guide effective use.

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?

The input schema has 100% description coverage (the 'symbol' parameter is documented as 'Stock symbol'), so the schema does the heavy lifting. The description adds marginal value by implying the symbol is used to fetch statistics for 'specific companies or stock symbols,' but does not provide additional syntax, format details, or constraints beyond what the schema already states. Baseline 3 is appropriate when schema coverage is high.

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's purpose: 'Analyze insider trading activity' with 'key statistics on insider transactions, including total purchases, sales, and trends for specific companies or stock symbols.' This specifies the verb (analyze), resource (insider trading activity), and scope (statistics for specific companies/symbols). It distinguishes from siblings like 'getLatestInsiderTrading' or 'searchInsiderTrades' by focusing on aggregated statistics rather than raw transactions or searches.

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 provides no explicit guidance on when to use this tool versus alternatives. It mentions analyzing 'specific companies or stock symbols' but does not clarify prerequisites, constraints, or differentiate from similar tools (e.g., 'getLatestInsiderTrading' for recent trades or 'searchInsiderTrades' for filtered searches). Usage is implied only by the general purpose statement.

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