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

With no annotations, the description carries the full burden and does useful work: it discloses that results are registry-sourced, off-market, and that unpublished registry fields are returned as null. It does not explicitly state read-only behavior or result pagination, but 'Search' and the null-handling note provide meaningful behavioral context beyond the schema.

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 and front-loads the core purpose. The long first sentence is dense but every clause contributes domain criteria; the second sentence adds a useful null-field note without filler.

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 an eight-parameter search tool with full schema coverage and no output schema, the description supplies important domain framing and null-value behavior. It stops short of explaining result shape or how filters combine, but the essential context for correct invocation is present.

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 100%, so all eight parameters are already documented. The description reinforces the meaning of the domain filters (age, margin, succession gap, countries) but does not add syntax or selection guidance beyond what the schema provides; 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?

The description clearly states a specific verb and resource: search registry-sourced European off-market succession targets. It adds concrete qualifying criteria (owners aged 60+, revenue/margin from filed accounts, no-manager-under-45 flag) and country scope, though it does not explicitly differentiate from siblings such as get_succession_target_details.

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 usage context is implied by the domain language: this is for finding succession targets across specified countries. However, it does not state when to use this versus get_succession_target_details or other search tools, nor does it mention prerequisites like API key handling beyond what the schema already says.

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