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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: it parses the structured Form D notice rather than text-searching, and enumerates the substantive contents returned (offering amounts, investors, first sale, exemption types, related persons, fees, SEC provenance). It does not say what happens for a non-Form D or malformed accession, which keeps it short of a 5.

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 resource and key format, then the routing guidance in priority order. The long mid-sentence enumeration of returned fields is dense but each item is informative; only minor tightening would be needed to reach 5.

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?

An output schema exists, so the description need not explain return values, yet it still summarizes payload contents usefully. Combined with the sibling routing and accession format, an agent has what it needs to call correctly; the only loose end is the unexplained CIK mention.

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% with a single required parameter that already carries a format example, so the schema does the heavy lifting and baseline 3 applies. The description's phrase "with or without the issuer CIK" hints at an additional input form that the schema does not expose, which adds slight ambiguity rather than meaning.

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 ("Read one SEC Form D securities offering notice (or D/A amendment)") plus the exact key it takes (accession number, with example). It also names what it is not: the generic EDGAR filing readers and form_d_search_issuers, so an agent can distinguish it from siblings without opening schemas.

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?

Explicit routing rules on both sides: prefer it over generic EDGAR readers when the accession is a Form D because it parses structured data instead of rendered text, and fall back to form_d_search_issuers when only the issuer name is known. Both the when-to-use and the when-not-to-use cases are covered.

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