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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds the 'FREE beta' pricing/availability note and 'quickly' implies a lightweight fast path, which is useful context. It does not disclose rate limits, result freshness, or what 'flags' returns, so it stays at baseline.

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 compact fragments with the availability note front-loaded and zero filler. It is efficient, though the extreme brevity is what creates the coverage gaps above rather than a deliberate trade-off.

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?

There is no output schema and no annotation of return shape, yet 'flags' is never explained — the agent cannot tell whether this returns forms, booleans, or scores. For a tool whose entire value is its output, the description omits the essential detail.

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%: cik is documented in the schema while limit (1-500) has no description anywhere. The description mentions no parameters at all, so the meaning and defaulting behavior of limit is left entirely unexplained; with a simple two-parameter surface this is merely adequate.

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 concrete verb ('flags') and a named resource ('recent filing forms') narrowed to corporate-action categories (tenders, offerings, proxies, material events). The purpose is clear, but it never differentiates itself from the sibling sec_recent_filings_basic or explains the 'basic' vs 'evidence' pair, so it stops short of 5.

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?

Provides no when-to-use guidance, no prerequisites, and no mention of alternatives. The _basic/_evidence sibling naming implies a tiering convention, but the description never says when this basic variant is preferable over sec_action_radar_evidence.

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