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. It explains that 'limit' controls the maximum number of filings returned, which adds some behavioral context. However, it does not disclose any side effects, privileges, or additional behavior, though as a read-only operation this is less critical. The description offers minimal but adequate transparency.

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 with a two-sentence purpose followed by a compact arg list. It front-loads the main purpose and avoids any wasted words, making it easy for an agent to parse quickly.

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?

There is an output schema present, so return values are covered externally. The description gives the essential purpose and parameter details, but it does not clarify what 'Recent' means (e.g., time window) or any sorting/ordering. For a simple retrieval tool, this is nearly complete, with only a minor gap about the recency definition.

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?

Despite 0% schema description coverage, the description clearly explains both parameters: 'ticker: Stock symbol' and 'limit: Maximum Form 4 filings to return.' This adds meaningful semantics beyond the bare schema types and defaults, fully compensating for the lack of schema descriptions.

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 a specific resource: 'Recent Form 4 insider transaction filings for a company.' It uses a specific verb 'get' and distinguishes itself from sibling tools like get_filings and get_filing_text by focusing on insider activity.

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 implies usage for insider transaction data based on the Form 4 specificity, but it does not explicitly mention when to use this tool versus alternatives, nor does it provide exclusions or alternative tool names. This is implied rather than stated.

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