insiders_funds

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

Annotations are absent, so the description must disclose all behavioral traits. It only states what data is retrieved but does not mention whether the data is historical or current, depth of coverage, or any quirks like data delay or units. For a read-only operation, it is minimally acceptable, but it adds no context beyond the literal action, leaving the agent uninformed about expected behavior.

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 a single, clear sentence with no filler or redundancy. It is appropriately front-loaded with the main action. However, it is so minimal that it lacks any supplementary structure (e.g., usage notes), but for a simple tool this conciseness is acceptable and does not detract from readability.

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 a single parameter and no output schema, the description provides the essential purpose but lacks contextual enrichment. It does not explain what constitutes 'fund ownership' relative to other ownership types or any further specifics. While not dangerously incomplete, an agent might need additional inference to fully understand the tool's applicability, making it 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 description coverage is 100%, as the parameter 'ticker' is documented with 'Stock ticker'. The description adds no extra detail about the parameter, such as accepted formats, examples, or constraints. With high schema coverage, a baseline of 3 is appropriate; the description does not enhance parameter understanding.

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 'Get fund ownership data for a ticker' clearly identifies the operation (get), the resource (fund ownership data), and the scope (for a ticker). It is specific and not tautological. However, it does not differentiate from closely related siblings like insiders_institutions or insiders_ownership, which could confuse an agent, so it loses a point.

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 such as insiders_institutions or insiders_activity. It purely states the action and target, leaving the agent to infer suitability based on name alone. No exclusions, conditions, or alternative references are given.

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