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

With no annotations, the description carries the burden, and it delivers meaningful context: SEC EDGAR source, open-market purchases/sales under Section 16, point-in-time/keyless access, and free. It does not disclose freshness or rate-limit details, which keeps it from a 5.

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 core question is front-loaded, and the analyst-corroboration example earns its place as usage guidance. Minor marketing/disclaimer text ('Free. Analytics, not advice.') adds little but does not seriously hurt navigability.

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 a simple two-parameter tool with an output schema, the description covers what, why, and when to use it. The unexplained since_days parameter is a real gap, and there is no mention of lookback window semantics, so overall completeness is adequate but not excellent.

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 no parameter descriptions (0% coverage), and the description only implies the ticker via 'this ticker'. 'since_days' is never mentioned or explained, so the description fails to compensate for the schema gap.

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 opens with a specific verb and resource: 'are company INSIDERS buying or selling this ticker?' It goes on to define the data source (SEC Form 4) and subjects (officers, directors, 10% owners), making it unmistakable and distinct from the analyst- and sentiment-focused sibling tools.

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?

It supplies an explicit use case: corroborate analyst sentiment with insider trading, including the bullish+buying and bullish+dumping scenarios. It stops short of naming alternatives or stating when not to use this tool, so it does not reach 5.

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