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

No annotations are provided, so the description carries the full disclosure burden. It does add real value by disclosing data provenance (registry-sourced, revenue/margin from filed accounts) and the null-handling behavior for unpublished fields. However, it says nothing about authentication needs (an api_key parameter exists), rate limits, or result ordering/pagination beyond the schema's limit.

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 dense sentences, front-loaded with the resource and scope, and the clause about nulls for unpublished fields is placed at the end where it belongs. It is information-rich without padding, though the parenthetical criteria list is heavy.

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 8 optional parameters, no annotations and no output schema, the description needs to do a lot of work. It covers the data domain and null semantics well, but omits any indication of the returned record shape and does not mention the optional api_key/auth requirement, leaving gaps for an agent invoking it.

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 the schema already documents all 8 parameters including defaults and examples, which sets the baseline at 3. The description restates the core filters (age 60+, margin source, under-45 board flag) but adds no syntax, format, or edge-case detail 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 names a specific verb (search) and a precisely scoped resource: registry-sourced European off-market succession targets, limited to UK, France and Norway. It even enumerates the target criteria (owners 60+, margin from filed accounts, no junior director flag), so the agent knows exactly what universe it queries. It does not explicitly contrast itself with siblings like search_insolvencies or get_succession_target_details, so it falls short of a 5.

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?

There is no explicit when-to-use guidance, no statement of when this is the wrong tool, and no reference to an alternative such as get_succession_target_details for full records. Domain scoping implies the usage context, but nothing in the text actually instructs the agent about selection.

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