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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description contributes the returned content shape (roles, amounts, filing links) but says nothing beyond annotations about pagination, rate limits, auth, sorting, or what happens at the 3650-day/100-trade caps.

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?

Two sentences, front-loaded with the verb and resource, followed by an enumeration of return contents and illustrative queries. Every element earns its place; the example list is slightly verbose relative to the short body but still useful.

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 an output schema present, the description needn't explain return values in detail, and annotations plus 100% schema coverage handle parameters and safety. It is close to complete for a read-only list tool; only ordering and result-size behavior are unaddressed.

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 100%, so all four parameters including open_market_only's semantic distinction are documented in the schema itself. The description only loosely gestures at the time window ('this year') and adds no syntax or default rationale, so baseline 3 applies.

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 a specific verb-plus-resource pair ('List and summarize insider trades (SEC Form 4) for one company') and enumerates the returned fields (buyer/seller, date, amount, role, filing link). It never names or contrasts a sibling such as get_insider_signal, find_insider_buying, or get_insider_person, so the tool is clear on its own but not differentiated from the crowded insider-tool family.

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?

Concrete example questions ('are insiders buying or selling NVDA?', 'show Tesla insider trades this year') give an agent a reliable trigger condition. What's missing is routing guidance: there is no statement of when to prefer get_insider_signal, find_insider_clusters, or get_insider_person, and no exclusions.

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