tool.description-collision
Not yet measured
This is a planned measured rule (SPEC §8). It is currently tier heuristic with no committed eval. It reports nothing and gates nothing until its battery passes the recomputed admission test. Running that battery costs API spend and requires explicit approval; it is out of scope for this build. The tier flips to enforced / measured only when the evidence is committed to evals/rules/tool.description-collision/ and verified in CI.
Claim
Two tools in one set describe themselves so similarly the model cannot reliably choose between them.
Rationale
Detector + committed eval land at M5 (SPEC §8); until the admission test passes, this rule reports nothing and gates nothing.
Fix
Differentiate the descriptions: name the distinct trigger for each tool, not the shared capability.
chaff explain tool.description-collision: same registry, offline, from the CLI.