Content
35%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is a templated shell: extensive process-discipline boilerplate and repeated description text, but almost no substantive guidance on how to perform pathology ROI selection, and its only executable reference (scripts/main.py) is missing from the bundle. Structure exists, but there is nothing actionable at its core.
Suggestions
Ship the referenced scripts/main.py (or remove all references to it) and document its real parameters — input WSI path, tissue type, magnification — with concrete values and example invocations.
Cut the verbatim description repetitions, the circular 'See ## X above' pointers, and the generic template sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status) that carry no domain information.
Replace the generic 5-step communication workflow with the actual ROI-selection procedure: how tissue/tumor regions are detected, thresholds used, and how output coordinates and crops are produced and validated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is noticeably padded: the description sentence is repeated verbatim in 'When to Use' and 'Key Features', circular no-op pointers appear ('See ## Prerequisites above', 'See ## Workflow above'), and generic template sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status with a stale 'Next Review Date: 2026-03-06') add no domain value. | 2 / 5 |
Actionability | The only concrete commands are 'python -m py_compile scripts/main.py' and 'python scripts/main.py --help', yet scripts/main.py does not exist in the bundle; there is no actual ROI-selection guidance — no thresholds, tissue-detection method, or real parameter values, and 'Edit the in-file CONFIG block' is hypothetical. | 2 / 5 |
Workflow Clarity | A 5-step Workflow with a Quick Check (py_compile) and an Error Handling/fallback section provides a sequenced path with some checkpoints, but every step is generic process discipline ('confirm the user objective… return a structured result') rather than the actual domain operation, and validation is not tied to real execution. | 3 / 5 |
Progressive Disclosure | Section headers give the body reasonable structure, but the sole bundle reference (scripts/main.py) is dangling — the file does not exist — and cross-references point to inline sections while boilerplate that serves no navigational purpose is inlined. | 3 / 5 |
Total | 10 / 20 Passed |