Get institutional investor 13F SEC filings for a given CIK or institution name. Default is Berkshire Hathaway (CIK 0001067983).
| Name | Required | Description | Default |
|---|---|---|---|
| cik | No | SEC CIK number (e.g. 0001067983 for Berkshire Hathaway) | 0001067983 |
| institution | No | Institution name to search for CIK (e.g. "Bridgewater Associates") |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It mentions a default CIK but fails to disclose behaviors like handling of multiple results, error conditions, rate limits, or data freshness. Only basic behavior is implied.
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?
Two sentences, zero wasted words. Effectively front-loaded with the core action and default, making it easy to scan. Every sentence earns its place.
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?
Despite lacking output schema and annotations, the description provides enough for basic understanding. However, it omits return format or structure of 13F filings, leaving gaps for an agent. Adequate but not comprehensive.
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 100% with descriptive parameter strings. The description adds minor context (default explanation and institution search purpose), but does not significantly enhance meaning beyond the schema. Baseline 3 is appropriate.
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 retrieves institutional investor 13F SEC filings using CIK or institution name, with a default. This verb-resource pair is specific and distinct from sibling tools like get_market_indices.
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 querying institutional holdings but provides no explicit guidance on when to use this tool over alternatives, nor any exclusions. Usage context is clear but without comparative direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct area: institutional holdings, market indices, and stock quotes, with no overlap in purpose.
All tool names follow a consistent 'get_' prefix followed by a descriptive noun phrase (institutional_holdings, market_indices, stock_quotes).
Three tools is appropriate for a focused market data server, covering key data points without being too sparse or too heavy.
Covers stock quotes, indices, and institutional holdings, but lacks historical data, fundamental metrics, or news, which are common in market data APIs.