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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond that by stating it pulls live from EDGAR, uses recency weighting, and returns specific cadence categories. No contradiction with annotations.

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?

The description is compact and front-loaded with the core behavior and output categories. The opening clause is somewhat redundant with the title, but the remaining sentences are dense and useful.

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?

Given there is no output schema, the description usefully communicates the data source, output concepts, and profile-specific behavior. Still, the semantics of limit and window_days and a more precise return shape are absent, so it is not fully complete.

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 descriptions cover domain and ticker, and the description adds meaning for buyer_profile by enumerating its tuning values. However, limit and window_days are never explained in the description, and with only 40% schema description coverage this is a meaningful gap.

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 names a specific verb/resource ('Pulls Form D / D-A filings live from EDGAR') and enumerates concrete outputs: a recency-weighted funding score, cadence hint categories, and buyer-profile-tuned action hints. This makes the tool easily distinguishable from sibling signal tools such as hiring_signal or compliance_signal.

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 description gives clear context for when this tool is appropriate: it surfaces funding signals from the public, authoritative record of private securities offerings and adapts output by buyer profile. However, it does not explicitly name sibling alternatives or state when-not-to-use conditions, leaving some routing to inference.

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