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

Beyond the readOnlyHint annotation, the description adds real behavioral context: it reads the store first to avoid the ~1,000-filing submissions-index ceiling, and it explains that records include the insider name, transaction code legend (P/S/A/M/F), shares, and dollar value, and that it returns 'insider_trade' envelopes. This tells an agent exactly what to expect.

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 front-loaded: the first sentence states the core purpose and scope, the second provides the sibling contrast, and the third adds behavioral detail and output shape. There is no filler, and every sentence earns its place.

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 the core invocation, the description is sufficiently complete: it identifies the required entity parameter, the per-company scope, the ordering, the behavioral advantage, and the output envelope. The only meaningful gap is the lack of guidance on optional start/end and limit parameters, which prevents a perfect score.

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 has 0% description coverage, so the description must compensate for the parameters. It only clarifies that entity accepts a ticker/name/CIK; it does not explain the start/end date formats, the meaning of limit, or how these interact with the 'newest first' ordering. Most optional parameters remain under-specified.

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 states a specific verb and resource: it returns recent insider (Form 4) transactions for ONE company, identified by ticker/name/CIK, newest first. It also explicitly contrasts itself with get_insider_window, making the tool's scope instantly distinguishable from its closest sibling.

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 explicitly names get_insider_window as the market-wide complement ('who bought the most across all issuers') and positions this tool as the per-company feed. This gives clear guidance on when to use this tool versus the alternative, leaving no ambiguity about scope.

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