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

Annotations already disclose that the operation is destructive, open-world, non-read-only, and idempotent. The description adds useful scope by saying it builds an evidence-based review and flags stale or missing data, but it does not explain destructive effects, external processing consent, or payment requirements beyond what structured fields provide.

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 tightly written sentences with no filler. The core purpose and the data-quality flag are front-loaded and easy to parse.

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 complex nested-input, destructive, open-world service with no output schema, the description is somewhat thin. It communicates the review scope and stale/missing-data behavior, but it does not explain output expectations, source reuse via sourceFields/sourceRunIds, or how this fits into the supplier-risk-to-negotiation workflow.

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 moderate at 67%, with useful descriptions for context, documents, constraints, idempotencyKey, paymentInvoiceId, and consent. The description adds no parameter-level guidance for sourceFields or sourceRunIds, so it does not compensate for those remaining gaps.

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 uses a specific verb and resource: 'Build an evidence-based supplier review' covering named risk domains. It is clearly a supplier-risk service, but it does not explicitly distinguish itself from siblings such as xrisk-monitor, xvendorbench, or xesg-scoring.

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 description states what the tool produces but gives no explicit when-to-use guidance, exclusions, prerequisites, or alternatives. An agent must infer usage from the tool name and sibling list rather than from the description.

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