Deterministically attach your triage verdicts to their findings and re-sort by exposure (highest first). Never suppresses. Pass the same 'findings' array you triaged plus a 'verdicts' array of { fingerprint, exposureScore, priority, rationale }.
| Name | Required | Description | Default |
|---|---|---|---|
| findings | Yes | The findings that were triaged. | |
| verdicts | Yes | One verdict per finding, keyed by fingerprint. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden and does well: it discloses deterministic behavior, the 'never suppresses' guarantee, and the exposure-based sort order. It stops short of describing return shape or error handling, but the most important behavioral traits are covered.
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 concise sentences cover the action, input requirements, ordering behavior, and a key guarantee. No redundancy or filler.
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?
No output schema exists, so the return value is not formally documented; however, 'attach ... to findings and re-sort' strongly implies an enriched/sorted findings array. The description covers input linkage, ordering, and the no-suppression behavior, with only error cases left unspecified.
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 has 100% coverage for both parameters, so baseline is 3. The description adds value by specifying that findings should be the same array already triaged and listing the required verdict fields ({ fingerprint, exposureScore, priority, rationale }), which clarifies the relationship between the two parameters.
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 ('attach') with a clear resource (triage verdicts to findings) and outcome (re-sort by exposure, highest first). It distinguishes itself from sibling tools like triage_findings, which would produce the verdicts, and remediate_findings, which acts on findings.
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 gives clear workflow context: pass the same findings array you triaged plus a verdicts array, establishing when this tool should be used. It does not explicitly name alternatives or exclusions, but the tie to a prior triage step is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clear and distinct purposes, but there is some overlap in the fix/verify area: apply_verified_patch, verify_fix, and remediate_findings all involve verification, which could cause an agent to hesitate on which to use. However, the descriptions differentiate them well (single-fix verification vs. snippet verification vs. batch remediation). Triage and apply_triage are clearly sequential.
All tool names follow a consistent verb_noun pattern in lower_snake_case (e.g., check_dependency, list_rules, suggest_hybrid). The only slight variation is apply_verified_patch with an adjective, but it still follows verb_noun structure and the pattern is otherwise uniform.
11 tools is well within the ideal 3-15 range and each serves a distinct function in the post-quantum analysis and remediation workflow: detection, explanation, triage, remediation, and scoring. No obvious redundant tools. The count feels well-scoped for the domain.
The tool set covers analysis (explain_finding, get_fix_examples), triage (triage_findings, apply_triage), remediation (remediate_findings, apply_verified_patch), and scoring (score_delta), but there is no scan tool. All triage/remediation tools require 'findings' arrays from an external scan_path command, which is not exposed as a tool in this server. This creates a significant gap in the workflow, as agents cannot initiate scans without an external dependency.