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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond annotations, including that private Rule 144A deals announced only in an 8-K are included, that 8-K filings cover the last 30 days, and that price reactions are measured at day 1, day 2, 1 week, and 1 month versus the prior close.

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 dense but front-loaded with the full scope of data returned and followed by practical example questions. The long enumerated list is justified by the complexity of the resource, though it could be slightly more scannable.

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 an output schema, four annotations, and full schema description coverage, the description is complete enough for correct invocation. It covers the return content, time windows, included filing types, and example use cases without needing to repeat parameter or output details already in structured fields.

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 documents both ticker and years. The description implies offering-history filtering but does not add meaning beyond the schema, such as clarifying how the years parameter interacts with the score or share-count trend, so the baseline of 3 is appropriate.

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 states a precise retrieval purpose: every stock offering, ATM program, convertible note, shelf registration, related 8-K filings, share-count trend, and dilution-risk score. It clearly distinguishes this tool from sibling tools focused on insider activity, financials, or market context, and an agent can identify the exact resource without opening the schema.

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?

It gives explicit example questions such as 'has SOFI diluted shareholders?' and 'what happened to the price after the last offering?', which clarifies when to use the tool. It does not name alternatives or exclusions, but the use context is clear enough for correct selection.

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