insiders_activity

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

No annotations are provided, so the description must carry the full disclosure burden. It does not state whether the result is a number, a time series, or a report, nor does it mention data source, frequency, or limitations. The description is a bare label rather than a behavioral disclosure.

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 a single, fluff-free sentence, but it is under-specified rather than efficiently concise. It omits critical context that an agent needs to understand the tool, so the brevity works against usefulness.

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?

With one parameter and no output schema, the description must explain what the data represents and what to expect. It provides none of that; the description essentially restates the tool name's implication ('net share purchase activity' vs 'insiders_activity') without elaboration. It is completely inadequate for an agent to call correctly.

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?

The schema describes the sole parameter 'ticker' as 'Stock ticker', and the description adds no further explanation of how 'net share purchase activity' relates to that ticker. Since schema coverage is 100%, the baseline of 3 applies, and the description does not elevate it with any additional meaning.

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 uses the verb 'Get' and a resource 'net share purchase activity', but the resource is vague and not clearly distinct from sibling tools like insiders_transactions or insiders_ownership. It does not specify whose activity (e.g., insiders, company insiders) or the time period, making it hard for an agent to understand the exact purpose.

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?

There is no guidance on when to use this tool versus the many related insiders tools in the sibling list. No conditions, alternatives, or exclusions are mentioned, leaving the agent to guess the tool's intended context.

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