getEquityOfferingsByCIK

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds nothing beyond that — no indication of how far back offerings go, whether results are paginated or how they are ordered, or what an offering record contains. For a read tool the annotations carry most of the weight, but the description contributes no incremental behavioral detail.

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 first sentence is front-loaded and does the real work; the second is generic investment framing that could be dropped from almost any finance tool without loss. It is short overall, but roughly half the content is filler rather than signal.

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?

For a single-parameter lookup with no output schema, the description should at minimum characterize the returned offering records (dates, amounts, offering type) since nothing else documents them. It conveys the domain but leaves the consumer guessing what 'detailed information' actually includes.

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?

With a single parameter and 100% schema description coverage, the schema already explains 'cik'. The description reinforces that the CIK identifies a company whose offerings are retrieved, but adds no format or normalization detail (padded vs unpadded, numeric vs string) beyond the schema.

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 and resource ('Access detailed information on equity offerings') and scopes it to companies identified by CIK. An agent can tell it retrieves offering records rather than prices or filings. It stops short of explicitly contrasting with siblings like getLatestEquityOfferings or searchEquityOfferings, so the boundary requires inference from the name.

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?

There is no when-to-use guidance: no mention of when to prefer this over getLatestEquityOfferings or searchEquityOfferings, and no prerequisites or exclusions. The second sentence ('Track offering activity and identify potential investment opportunities') is marketing framing, not invocation guidance.

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