get_insider_activity

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the data source (Finviz), the type of data returned, and the fields shown, which gives a reasonable picture of the tool's behavior. However, it does not disclose whether the data is delayed, whether it covers only recent activity vs. full history, or any rate limits or pagination behavior. For a read-only data retrieval tool, this is adequate but not rich.

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 concise and front-loaded with the core purpose, followed by the data fields and a use case. The Args section is minimal but appropriate for a single parameter. It earns a 4 rather than 5 because the use-case sentence and the sibling distinction could be slightly more integrated, but there is no waste.

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?

The tool has a single parameter, an output schema, and a clear sibling distinction. The description covers the data source, the fields returned, and the use case. It does not mention data freshness, pagination, or any limitations, but for a simple single-ticker lookup with an output schema, the description is largely complete. A 4 is appropriate because the missing behavioral details (e.g., how far back 'recent' goes) could matter to an agent.

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 0%, so the description must compensate. It does explain the single parameter 'ticker' as 'Stock ticker symbol' in the Args section, which adds minimal meaning beyond the schema's 'Ticker' title. Since there is only one parameter and it is a standard ticker symbol, the description is sufficient but not detailed (e.g., no format examples like 'AAPL' or 'MSFT').

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 recent insider trading activity (buys/sells) from Finviz, and lists the specific data fields returned (insider name, relationship, transaction type, date, share count, dollar value). It also distinguishes itself from the sibling get_insider_filings by noting that tool covers SEC Form 3/4/5 filings with EDGAR links.

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 a clear use case ('useful for gauging management conviction') and explicitly names the alternative for SEC filings (get_insider_filings). It does not state when not to use this tool beyond the SEC filings distinction, but the context is sufficient for an agent to choose between the two insider-related tools.

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