searchEquityOfferings

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety profile is covered. The description only adds that results cover 'recent share issuances' — modest extra context, with no detail on result size, ordering, or rate limits.

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?

Only two sentences, but they carry marketing filler ('Easily', 'stay informed on company fundraising activities') that does not help invocation. The operative content could be tightened to a single line.

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 simple one-parameter read tool with full schema coverage and clear annotations, the description covers purpose and rough return content ('recent share issuances'). Little more is needed, though it could note result ordering or whether the search is fuzzy.

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 the single 'name' parameter is fully documented in the schema. The description restates that name-or-symbol input is accepted but adds no extra semantics such as partial matching or ticker format. Baseline 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?

States a specific verb (search) and resource (equity offerings) plus the search keys (company name or stock symbol). It is distinguishable from getLatestEquityOfferings and getEquityOfferingsByCIK by the free-text search, though it doesn't name those siblings explicitly.

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?

Implies usage via 'search by company name or stock symbol,' but gives no explicit when-to-use vs getLatestEquityOfferings or getEquityOfferingsByCIK, and no conditions or exclusions. The agent must infer the routing.

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