get_8k_events

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

With no annotations, the description carries the full burden; it implies a read operation ('Get') but never states auth or rate-limit behavior. It does add real value by disclosing that events include SEC item codes and a filing_url so results can be verified, which is provenance context beyond the schema.

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?

Front-loads the purpose sentence and then lists args and returns compactly, with no filler. The Returns section partially re-states what the output schema already carries, but it is short and adds provenance framing.

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?

An output schema exists, so return values needn't be explained, yet the description gives an accurate sketch plus the filing_url trust angle. For a 3-param read tool with no annotations, the only real gap is the absence of usage/routing guidance.

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 0%, and the description compensates by documenting all three params: ticker_or_cik meaning, ISO date format for since, and the 1-200 range plus default for limit. It stops short of saying what happens on invalid input or how ticker vs CIK resolution behaves.

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?

States a specific verb and resource ('Get 8-K material events with SEC item codes for a company'), which is far more precise than a generic filings tool. It does not explicitly distinguish itself from the sibling get_recent_filings, which could plausibly also surface 8-Ks, so an agent must infer the boundary.

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?

No when-to-use, when-not-to-use, or alternative-routing guidance is given. The date and limit notes describe parameter mechanics rather than selection criteria against siblings like get_recent_filings or get_financials.

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