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

No annotations are provided, so the description must carry the transparency burden. It does convey a read-only retrieval behavior with 'search' and 'Access detailed information about recent share issuances', but it omits details about result structure, matching semantics, pagination, or limitations.

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 two sentences, with the action and resource in the first sentence. Minor filler such as 'Easily' and 'to stay informed on company fundraising activities' could be trimmed, but overall it is efficient.

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 and a large sibling tool set that includes closely related offerings tools, the description leaves important gaps: it does not mention return fields, list vs. single result, or alternative tools. The phrase 'detailed information' is too vague for an agent to know what to expect.

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?

The input schema already documents the single 'name' parameter at 100% coverage. The description echoes 'company name or stock symbol' and adds equity-offering context, but does not provide extra parameter-level guidance 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 uses the specific verb 'search', identifies the resource as 'equity offerings', and names the query keys 'company name or stock symbol'. This clearly distinguishes it from sibling tools like getLatestEquityOfferings or getEquityOfferingsByCIK.

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?

The intended use is implied: use when you want to search equity offerings by company name or stock symbol. However, there is no explicit when-not guidance or mention of nearby alternatives such as getEquityOfferingsByCIK or getLatestEquityOfferings.

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