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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established and the bar for the description is lower. The description adds useful behavioral context beyond that: results are restricted to announced deals, and enterprise value is included only 'where disclosed', signaling partial data coverage. It stops short of describing result limits or deduplication, but that is minor given the annotation coverage.

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?

Two sentences with no filler: the first defines the dataset and enumerates its returned fields, and the second lists every filter dimension. The most important scoping information (announced, by independent sponsors) is front-loaded. Every clause earns its place.

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, the description compensates by enumerating the returned fields (dates, enterprise value range, structure, parties, source), so an agent knows what to expect from results. The full filter surface, read-only profile, and open-world constraint are covered across the description and annotations. Minor gaps remain — default result size and value formatting are not mentioned — but nothing blocks a correct first invocation.

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 57%, leaving limit and since undocumented in the schema itself. The description's filter list maps semantic intents to parameters ('sponsor, target, type, state, since-date or name text'), which clarifies that query is name-based text matching and since is a date. It does not fully compensate for the undocumented limit parameter, but the default and bounds are present in the schema, so the combination is adequate.

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 specific resource ('announced acquisitions, recapitalisations and exits by independent sponsors') with precise scope qualifiers that let an agent distinguish it from overlapping siblings such as search_pe_transactions, get_independent_sponsor, and search_sponsor_capital_providers without opening their schemas. The second sentence names the search/filter verb and the dimensions it operates on. This is a specific verb + resource with implicit sibling differentiation.

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 case is implied by the scope — use this when you need announced deal activity by independent sponsors — so an agent can infer when it applies. However, there is no explicit when-to-use/when-not-to-use guidance and no alternative tool is named, which is a real gap given 60+ siblings and the potential overlap with search_pe_transactions or search_events. The definition leaves routing decisions entirely to the agent.

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