Retrieve sovereign wealth fund (SWF) US equity holdings — Norway GPFG, GIC Singapore, ADIA, PIF. Tracks position changes for the world's largest state-backed investors.
Args: fund: Optional SWF name filter (e.g. "Norway", "GIC", "ADIA") quarter: Informational; the actor returns the most recently reported quarter per fund.
| Name | Required | Description | Default |
|---|---|---|---|
| fund | No | ||
| quarter | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful context: it is for state-backed investors, tracks position changes, and quarter parameter returns most recent quarter per fund. No contradictions with annotations.
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 three sentences: first sentence states purpose with examples, second adds context, third details parameters. No wasted words, front-loaded with key information.
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?
No output schema exists, so description should document return structure. It mentions retrieving holdings and tracking changes, but does not specify return fields, format, or pagination. For a retrieval tool, this is incomplete.
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 0%, so description must compensate. It explains 'fund' is an optional SWF name filter with examples, and 'quarter' is informational returning the most recent quarter. This adds meaning beyond the bare schema, though acceptable values for fund could be more exhaustive.
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 verb 'retrieve' and the resource 'sovereign wealth fund (SWF) US equity holdings', listing specific funds (Norway GPFG, GIC Singapore, ADIA, PIF). It distinguishes itself from sibling tools that deal with other financial data types like insider trades or 13F filings.
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 mentions optional parameters and explains the quarter parameter is informational, but does not provide explicit guidance on when to use this tool versus alternatives like get_form_13f_holdings. No when-not-to-use or alternative tool comparisons are given.
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 regulatory filing or financial data type with clear, non-overlapping descriptions. Even similar concepts like 13F holdings vs. delta are well-differentiated.
Most tools follow a consistent 'get_<noun>' pattern, with a single exception 'detect_insider_cluster'. Overall naming is predictable and readable.
17 tools is slightly above the ideal 3-15 range but justified by the broad domain of regulatory filings and financial data. Each tool serves a clear purpose.
The server covers a comprehensive set of regulatory filings (13F, Form 4, 8K, etc.) and additional financial data (analyst targets, options, short interest). Minor gaps like Form 144 are acceptable given the scope.