get_insider_filings

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

No annotations are present, so the description must carry the behavioral burden. It usefully discloses the output contents and data source ('Powered by edgartools' Form4 parser'), but it does not explicitly state read-only/side-effect behavior, authentication needs, or pagination/limitations; for a get tool this is adequate but not complete.

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 compact and well-structured: purpose, output details, alternative usage, then parameter definitions. Every sentence earns its place and the key purpose is front-loaded.

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 two-parameter read tool with an output schema, the description covers the essential context: what filing types are returned, what data fields are included, the underlying parser, and the sibling alternative for human-readable data. It does not mention edge cases or limits, but these are less critical given the simple parameters and output schema.

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 for the bare property titles. The Args section adds functional meaning: ticker is a 'Stock ticker symbol' and max_results is the 'Number of filings to return.' This is sufficient for both parameters, though not deeply detailed.

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 opens with a specific verb and resource: 'Get insider trading SEC filings (Form 3, 4, 5) with structured data.' It names the exact form types and the structured-data nature, which distinguishes it from sibling tools like get_sec_filings and get_filing_text.

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?

It explicitly identifies an alternative: 'For a human-readable summary of recent buys/sells with dollar values, use get_insider_activity (Finviz) instead.' This gives agents a clear when-to-use/when-not-to-use rule without requiring them to inspect other tools.

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