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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a critical behavioral fact: 8-K classification was retired on 2026-08-27, so nine named fields are NULL or False for recent filings and hold historical values only for older ones. It also tells the agent not to present or infer those values and to steer users to filing_url, which materially changes how results must be handled.

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 mode behavior is front-loaded in the first sentence, and the deprecated-field caveat is placed where an agent will read it before formatting output. The multi-line field enumeration and the doubled 'do not present... do not infer' instruction are slightly verbose but justified by the risk of misreporting stale classifications.

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 no output schema, the description carries the return-value burden and does explain what the two modes return, plus a strong caveat about the meaning of returned fields. It omits pagination/limit behavior and any note on how many filings the feed returns, which an agent calling this repeatedly would want.

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 coverage is 50% and the description does meaningful work for ticker, explaining not just that it filters but that it changes the return set to filings matched against preceding insider purchases. The limit parameter is unexplained in both the schema and the description, leaving one 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 names a specific verb and resource (recent SEC Form 8-K filings correlated with insider buying) and defines two distinct modes based on whether a ticker is supplied. It stops short of naming the sibling tools an agent might confuse it with (search_filings, get_filing), so it is clear but not sibling-differentiating.

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 clearly states the two usage contexts: pass a ticker to get that company's 8-Ks matched against preceding insider purchases, omit it for the general recent-8-K feed. No explicit when-not-to-use or named alternatives are given, so the guidance is strong but not exhaustive.

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