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

Annotations already declare readOnly, idempotent, non-destructive, and open-world. The description adds useful context that results are 'decoded and ranked' and include a link to the filing, plus a non-advisory disclaimer. It does not disclose ranking criteria, pagination, or auth/rate-limit behavior, so it adds modest value over the structured hints.

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-loaded with the core purpose, then a dense but useful enumeration of event types. Single sentence plus a short disclaimer; no filler, though the event list is lengthy.

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 need not explain return values, and annotations carry the safety profile. Scope and covered event types are well explained; only explicit sibling-routing guidance is missing for full completeness.

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 100%, and the schema documents both 'ticker' and the 'days' range (7 to 365). The description adds no parameter syntax or defaulting details beyond what the schema provides, making the baseline 3 appropriate.

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 (lists material corporate events from SEC 8-K filings) and enumerates the exact event types covered, so the agent knows what it will receive. This is clearly distinguishable from siblings like get_company_financials or get_company_brief.

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 purpose implies when to use it (surfacing material 8-K events for a company), but there is no explicit comparison or routing guidance against siblings such as get_company_brief, get_company_financials, or list_insider_trades. No exclusions or prerequisites are stated.

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