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

Annotations already disclose readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=true, but the description adds nothing about them — no word on what is destroyed, that inputs are sent to an external inference provider requiring explicit consent, or that runs are keyed/idempotent. "Evidence and gaps to review" is the only added context and it is thin for a destructive, open-world tool.

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 front-loaded sentence with no filler, and the core operation leads. It is efficient but borders on under-specification given the tool's structural complexity.

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 nested six-parameter tool with a required consent flag, idempotency key, and destructive/open-world annotations, the one-liner leaves major questions unanswered: how runs are chained via sourceRunIds, how the combined 75,000-character and 45,000-per-field limits affect input size, and what a result contains. With no output schema, the description's "evidence and gaps" hint partially covers the return shape but not enough.

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 coverage is 67%, below the high-coverage threshold, so the description should carry weight it does not: it never mentions the rubric/weights requirement, the supplier responses, disqualifiers, or source run chaining. The two parameters with no schema description at all, sourceFields and sourceRunIds, go entirely unexplained in both places.

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?

States a specific verb and resource — "Compare supplier bids" — plus the method (weighted scoring matrix) and outputs (evidence and gaps). It is clear enough to distinguish from drafting tools like xrfp-drafter, though it never names the nearest sibling such as xvendorbench or xmatch-supplier-shortlist to draw the boundary explicitly.

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 when-to-use guidance, no prerequisites, and no alternatives named despite a crowded sibling set containing xvendorbench, xmatch-supplier-shortlist, and xclause-risk-scoring. The agent must infer from the tool name alone whether this or a sibling is appropriate.

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