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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuine value beyond them by disclosing that returned profiles are 'abstract' and that private counterparties/contacts are stripped. It omits result ordering, pagination behavior (default 10 / max 20), and whether all filters combine with AND semantics.

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?

A single tight sentence with the key scoping fact front-loaded and no filler. It is efficient rather than verbose, though its brevity borders on under-specification given 13 undocumented parameters.

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 13-parameter search tool with no output schema and no parameter descriptions, the definition does not say what filters exist, how results are ranked or truncated, or what a returned profile contains. An agent could call it, but only by guessing at most of the query surface.

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?

The schema has 13 parameters with 0% description coverage, so the description carries the full burden and supplies nothing about them. Self-explanatory names like 'country' and 'product' help slightly, but ambiguous ones ('capacity', 'moq', the 'source_language' vs 'preferred_language' pair, 'canonical_concept_id', 'delivery_geography') are left entirely undefined.

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?

Names a specific verb and resource ('Search ... abstract public opportunity profiles') and flags that results exclude private counterparties and contacts. It is distinguishable from the sibling search_* tools by resource, though it never explicitly contrasts itself with search_manufacturers, search_products, or request_opportunity_match.

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?

Says nothing about when to pick this tool over search_manufacturers/search_products/search_suppliers or the state-changing request_opportunity_match. The only scoping statement ('private counterparties and contacts excluded') describes what results contain, not when to use the tool.

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