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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description usefully adds that only public projections are touched and that no scoring changes or autonomous research occur, reinforcing data-scope boundaries beyond the annotations. It still leaves the actual matching/filter behavior opaque.

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?

Only two short sentences, so nothing is bloated. However, the front-loaded sentence is the least informative part, and the second sentence is framed entirely as negation, spending the limited budget on what the tool is not rather than what it does.

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 13 undocumented parameters, no output schema, and no explanation of return shape or matching semantics, the description is nowhere near sufficient for correct invocation. An agent would have to guess at filter semantics and result format.

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 0% across 13 parameters (moq, country, product, capacity, keywords, hs_cn_code, certification, specification, source_language, preferred_language, canonical_concept_id, delivery_geography, limit). The description adds no meaning for any of them — no format hints, no interaction rules, no indication of which filters combine or are recommended.

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 phrase "Filter only permitted public opportunity projections" hints at filtering public opportunity data, but the wording is jargon-heavy and never states plainly that this performs an opportunity search/match. It offers no differentiation from the sibling `search_opportunities`, so an agent cannot tell which to choose.

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 a scope exclusion (only permitted public projections, no private/customer matching), but no positive guidance on when to use this instead of `search_opportunities` or the other search_* siblings. The agent must infer the triggering conditions entirely.

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