Exempt Offerings (Form D)

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

Annotations only declare readOnlyHint=true, so the description carries the real burden — and it delivers. The warning that ongoing offerings are re-noticed through D/A amendments that RESTATE the same offering, with a dedup rule (group by first-sale date and offering amount, keep only the latest notice), is a genuinely valuable behavioral caveat that prevents double-counting capital raised.

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?

It is a fairly dense block, but it is front-loaded (what it returns first, then the critical D/A caveat, then the use context) and nearly every sentence earns its place. The enumeration of returned fields is long but necessary given no output schema.

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 must describe the return payload — and it enumerates issuer, date of first sale, offering amount (dollar figure or 'Indefinite'), amounts sold and remaining, minimum investment, investor count, exemptions, D/A amendment status, and accession number. Nothing material 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 coverage is 100% and all five parameters are well documented in the schema (offset, ticker, toDate, fromDate, maxResults with defaults and clamping rules). The description adds no parameter-level syntax or format detail beyond what the schema already provides, so the baseline 3 is correct.

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 and resource — 'Get recent exempt securities offerings (private placements) for a company from SEC Form D notices' — and lists the exact fields reported. No sibling tool covers Form D offerings, so an agent can immediately tell this is the one tool for private-placement capital raises.

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?

'Use this to track how a company is raising private capital alongside its public filings' gives a clear use context, and the D/A grouping guidance tells the agent how to consume results correctly. It stops short of naming explicit alternatives or when-not-to-use conditions, so it's clear but not fully routing.

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