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

With no annotations, the description carries the full burden, and it does add two real behavioral facts: it never contacts parties or moves money, and it enforces a signed-mandate gate. However, it does not say whether the tool is read-only or persists matches, what 'report eligibility gaps' produces, or what the mandate gate requires in practice.

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 with the core action front-loaded, and the constraint sentence kept short. Some jargon ('strong visible semantic official-award evidence') costs a little clarity but nothing is redundant.

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?

There is no output schema and no annotations, so the description must carry everything, and it covers purpose plus key safety constraints. It still omits parameter meanings and any indication of what a match result or eligibility gap report contains, leaving an agent under-informed for a 3-parameter tool.

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% for all three parameters (limit, query, buyer_limit). The description hints at query semantics via 'exact CPV or strong visible semantic' matching, but limit and buyer_limit are entirely unexplained, so the description does not compensate for the coverage gap.

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?

Specific verb (match) and resources (qualified live Buyer demand to suppliers), plus the matching criteria (exact CPV or semantic official-award evidence). It is distinguishable from siblings like qualify_buyer_demand and verify_supplier_public_evidence, though it never names an alternative to differentiate further.

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?

No explicit when-to-use statement, no prerequisites, and no named alternatives among the many sibling tools. The phrase 'qualified live Buyer demand' weakly implies this runs after qualification, but the agent must infer when to pick this over qualify_buyer_demand or verify_supplier_public_evidence.

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