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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and scope profile is fully covered by structured data. The description adds only the input-identity requirement and the non-exhaustive-search constraint; it says nothing about behavior when query is empty despite the schema defaulting to "".

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?

One compact sentence with the positive capability front-loaded and the scope exclusion trailing. Every clause carries information, though the run-together token "astockevent" and the slightly awkward phrasing slightly reduce readability.

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 one-optional-parameter, read-only lookup with an output schema present, the description covers what the tool does, what input forms are valid, and what it will not do. Nothing essential to correct invocation is missing, aside from empty-query behavior, which is minor given the default.

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 0% — the single "query" parameter is documented only as a title and default. The description compensates well by specifying the accepted value forms: a name, a verified ticker or alias, or a CIK number, which materially changes how the agent fills the parameter.

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 gives a specific verb and resource ("Find ... acquisitions") and enumerates the three identifier forms the lookup accepts (name, verified ticker/alias, CIK). It is clearly a targeted lookup rather than a generic listing, though the wording drifts from the tool name ("list_deals" vs "find acquisitions"), which costs a little precision.

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 clause "not all-market search" tells the agent when this tool is inappropriate, which is real guidance. However, it names no alternative tool for broad or all-market discovery, and it never states the minimum required input, so the agent must infer that some identifier is expected.

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