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. It states the tool is for searching/tracking, implying a read-only operation, but does not disclose behavioral traits such as rate limits, authentication needs, response format, or pagination. For a search tool with zero annotation coverage, this is a significant gap in transparency.

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: one stating the purpose and API, another adding context. It avoids redundancy and is front-loaded with key information. However, it could be slightly more concise by integrating the context into the first sentence.

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 moderate complexity (search with one parameter), no annotations, and no output schema, the description is minimally adequate. It covers the purpose but lacks details on usage guidelines, behavioral traits, and output expectations. It meets basic requirements but has clear gaps for effective agent 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, with the 'name' parameter clearly documented as 'Reporting person's name to search for.' The description adds no additional parameter semantics beyond what the schema provides, such as format examples or search behavior. Baseline 3 is appropriate when the schema does the heavy lifting.

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: 'Search for insider trading activity by reporting name' (verb+resource). It specifies 'track trading activities of specific individuals or groups involved in corporate insider transactions,' which adds useful context. However, it does not explicitly differentiate from sibling tools like 'searchInsiderTrades' or 'getLatestInsiderTrading,' missing a clear distinction.

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 guidance on when to use this tool versus alternatives. It mentions 'track trading activities' but does not specify prerequisites, exclusions, or compare it to sibling tools like 'searchInsiderTrades' or 'getLatestInsiderTrading.' This leaves the agent without clear usage context.

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