get_insider_trades

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

With no annotations, the description carries the full behavioral burden. It usefully adds ordering ('newest first') and clarifies the report type via the SEC Form 4 analogy, but it never states that this is a read-only lookup, nor does it mention pagination, rate limits, or error 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 short, front-loaded, and every sentence adds useful context: the report type, the SEC Form 4 analogy, the covered persons, and the sort order. Minor redundancy between 'executive and major-shareholder ownership reports' and 'holdings and changes by directors, officers, and 10%+ holders' keeps it from a 5.

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?

An output schema exists, so return values need not be explained. However, for a tool with no annotations and 0% schema description coverage, the description is incomplete: it omits the company identifier format, the limit semantics, and any differentiation from get_major_shareholder_changes.

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 explain the parameters, but it says nothing about the required 'company' identifier format (ticker, name, Korean company name?) or what 'limit' controls and its maximum. It only broadly implies the domain, leaving both parameters semantically underspecified.

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 gives a specific resource (executive and major-shareholder ownership reports) and a useful analogy (Korea's SEC Form 4), with clear scope (directors, officers, 10%+ holders). It does not, however, explicitly distinguish this from the sibling get_major_shareholder_changes, which appears to overlap.

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 content implies when the tool is relevant, but there is no explicit 'use this when' guidance and no exclusion or alternative named. Given the overlapping sibling get_major_shareholder_changes, the lack of routing guidance is a meaningful gap.

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