Content
50%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 has a sound overview-plus-references structure and some genuinely executable CLI/KQL content, but it is undermined by broken navigation (three of six service guides reference nonexistent files), an unlinked scripts/ bundle, pseudocode MCP invocation blocks, and repeated content across sections. All four dimensions land mid-scale as a result.
Suggestions
Fix or remove the broken routing targets: troubleshooting/aks/aks-troubleshooting.md, troubleshooting/compute/vm-troubleshooting.md, and troubleshooting/messaging/README.md do not exist in the bundle — either add these files or repoint the AKS, Compute, and Messaging rows (and the Routing bullets) to real paths (progressive_disclosure, actionability).
Make the bundled scripts actionable: Rule 7 says "Prefer bundled diagnostic scripts" but never names them — list the actual paths in scripts/ (e.g. scripts/aks-baseline.sh, scripts/test-messaging-connectivity.sh) in the routing table or rules, and replace the pseudo-invocation MCP blocks ("mcp_azure_mcp_applens / intent: ... / command: ...") with the real tool-call format (actionability).
De-duplicate the body: drop the "AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE" banner, the Triggers section that restates the frontmatter WHEN list, the repeated CLI block under "Check Azure Resource Health", and the trailing References section that duplicates the routing-table links; use the freed tokens to add verification checkpoints to the Quick Diagnosis Flow (conciseness, workflow_clarity).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The core tables and commands are dense, but several sections are redundant or padded: the "AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE" banner, a Triggers section restating the frontmatter WHEN list, the "Check Azure Resource Health / Using CLI" block repeating "az resource show --ids RESOURCE_ID" and "az monitor activity-log list -g RG --max-events 20" verbatim from Quick Reference, and a References section duplicating the routing-table links. Not 2 because there is no concept-explanation fluff; not 4 because the duplication spans multiple sections rather than being minor instances. | 3 / 5 |
Actionability | There is genuinely executable content ("az containerapp logs show --name APP -g RG --follow", the App Insights KQL query), but the MCP blocks are pseudo-invocation format ("mcp_azure_mcp_applens / intent: ... / command: ...") rather than actual tool-call syntax, Rule 7 says "Prefer bundled diagnostic scripts" without naming any of the 12 scripts in scripts/, and three of the six routing targets point to files that do not exist. Not 4 because these gaps exceed "minor"; not 2 because concrete, runnable CLI/KQL guidance is present. | 3 / 5 |
Workflow Clarity | The 5-step Quick Diagnosis Flow ("Identify symptoms - What's failing?" through "Investigate recent changes - What changed?") plus the ordered Rules give a coherent sequence, but steps are generic prompts with no validation checkpoints or error-recovery guidance — e.g. "az resource show --ids RESOURCE_ID" is labeled "Check resource health" even though it returns resource properties rather than health status, so step outcomes cannot be verified. Not 4 because checkpoints are missing entirely; not 2 because a clear, ordered sequence is present. | 3 / 5 |
Progressive Disclosure | The overview-plus-references structure is well signaled (service routing table pointing one level deep to references/app-service/README.md, references/functions/README.md, etc.), but three of the six guide paths referenced in the body ("troubleshooting/aks/aks-troubleshooting.md", "troubleshooting/compute/vm-troubleshooting.md", "troubleshooting/messaging/README.md") do not exist in the bundle, and the 12 files in scripts/ are never linked from the body. Not 4 because broken navigation targets and an unlinked scripts directory are more than minor organization gaps; not 2 because the structure is present and clearly signaled. | 3 / 5 |
Total | 12 / 20 Passed |