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

Annotations only supply readOnlyHint=true, yet the description adds substantial behavior: the exact return shape {summary, count, days, industry, offerings}, the caveat that total_offering_amount is a ceiling rather than money raised, the quarterly posting lag, and limit default/cap. This is rich disclosure well beyond the annotation.

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 scope, then tight supporting notes on return shape, the ceiling caveat, the empty-window pitfall, and limits. Every sentence carries actionable information with no filler.

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 supplies the return keys and the key semantic traps (ceiling vs raised, empty window by construction), plus limits and data source. Nothing an agent needs to call it correctly is missing.

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% and the schema itself already explains the days window construction, the limit default/cap, and the industry filter. The description reinforces the days caveat and limit cap but adds little semantic detail not already in the schema, so baseline 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?

States a specific verb+resource (recent SEC Form D private-placement filings), names the source data set, and specifies ordering (newest first) and optional scoping. It is clearly distinguishable from siblings like get_insider_activity or ol_13f_filer_search.

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?

Gives strong operative context: optional industry/date-window scoping and a critical warning that a short `days` window is empty by construction, not evidence of no filings. It does not explicitly name an alternative sibling tool, so it stops short of a 5.

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