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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description only needs to add behavior. It usefully discloses the high-signal filter (importance ≥ 60) and the event categories, but says nothing about ordering, pagination, or what an entity with no qualifying events returns.

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 tool's identity and scope. The event list is long but each item defines the boundary of what counts as 'material,' so every element earns its place.

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 burden of describing returns, and it does so by enumerating the event categories emitted. It stops short of describing the shape, ordering, or empty-result behavior, but for a filtered-feed tool the scope disclosure is largely sufficient.

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% – both 'key' (accepted identifier types) and 'days' (default 180, max 730, some sources undated) are fully documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 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 states a specific resource ('cross-vertical alert feed for one entity') and enumerates the event categories it surfaces (Class I recalls, 13D filings, insider sales, restatements, etc.), so an agent knows exactly what it yields. It does not, however, explicitly contrast itself with near siblings like entity_timeline, cross_vertical_active, or company_risk_flags, which weakens true disambiguation.

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?

Usage is only implied: the framing as an 'alert me' feed and the importance ≥ 60 threshold suggest it is for surfacing high-signal events on a known entity. There is no statement of when to prefer it over alternatives (e.g. entity_timeline for a full chronology) and no prerequisites.

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