get_sec_form4_filings

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

No annotations are provided, so the description carries full burden. It discloses the tool retrieves real data from SEC.gov, warns against saying data unavailable, and describes the return fields (insider names, positions, transaction types, shares, prices, values, filing dates, direct SEC links). No destructive behavior is mentioned, which is appropriate for a read-only tool.

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 lengthy and contains redundant elements like emojis, all-caps warnings, and extensive examples. While structured with sections, it could be more concise by trimming the 'PRIMARY TOOL' list and example queries without losing clarity.

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 no output schema, the description explicitly lists the return fields (insider names, positions, transaction types, shares, prices, values, filing dates, direct SEC links). It covers both operating modes and all parameters thoroughly, making it well-rounded for a read-only tool.

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%, but the description adds significant contextual meaning beyond the schema. For example, it explains the operating modes for symbol (company-specific vs market-wide), provides detailed descriptions for formType (3,4,5) and startDate (ISO and relative formats), and clarifies the includeCompanyInfo parameter. This is above the baseline of 3.

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 SEC Form 4 insider trading filings from EDGAR, specifies two operating modes (company-specific vs market-wide), and uses specific verbs like 'get' and 'returns'. It distinguishes itself as the primary tool for Form 4 queries, providing clarity on its scope.

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 explicit usage guidance with example queries and lists what queries it is the primary tool for. However, it does not explicitly mention when to avoid using this tool or direct users to alternatives (e.g., get_insider_trades sibling) for potentially overlapping functionality.

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