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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds tier/beta context and lists the returned artifacts, but says nothing about rate limiting, authentication expectations, or result caps beyond what annotations provide.

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?

Three tight fragments with no filler, and the distinguishing content (what the signals carry) follows immediately. Leading with 'FREE beta' is marginally wasteful since it is not decision-relevant for invocation.

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 sensibly enumerates the returned fields, which is the right thing to cover. But it omits the basic-vs-evidence tier difference, the meaning/bounds of 'limit', and pagination or result-volume behavior, leaving gaps for a two-parameter retrieval tool.

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 only 50%: 'cik' is documented in the schema, but 'limit' (max 500) has no description anywhere, and the description supplies no parameter information at all. With a low coverage ratio the description was expected to compensate, and it does not.

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?

It names a specific resource ('Form-based corporate-action signals') and enumerates the payload it returns (confidence, accession numbers, filing URLs, provenance), so an agent knows what it will get. However it uses no verb and never distinguishes itself from the sibling sec_action_radar_basic, so the tier boundary has to be inferred from the name alone.

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?

There is no statement of when to call this versus sec_action_radar_basic, no prerequisite (e.g. valid CIK format or SEC rate/identity requirements), and no exclusion conditions. 'FREE beta... Intended future paid tier' is licensing information, not usage guidance.

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