Skip to main content
Glama

score_initiative

Read-onlyIdempotent

Score one AI initiative deterministically from known industry, revenue, function, tier and readiness, returning Accelerate, Fix or Stop with modelled EUR benefit ranges and audit trail.

Instructions

Canonical-field scorer for one AI initiative. CALL THIS when industry, revenue_eur, function, ai_tier and readiness are already known, or when re-scoring with measured pillar evidence. For a proposal written in ordinary business language, call assess_ai_initiative first; it resolves these fields and asks for anything missing. Pillar scores remain optional: missing pillars are estimated deterministically, reported through pillar_basis, and reduce decision score, while a fully estimated pass can never return Accelerate. Returns Accelerate, Fix or Stop, modelled gross and readiness-adjusted EUR benefit ranges, decision score, sensitivity, assumptions and an audit trail. Use score_portfolio for several initiatives and diagnose_process for measured waste in an existing process. Deterministic calculation with no authentication. Anonymous usage telemetry may be sent; set AIBVF_TELEMETRY_DISABLE=1 to opt out.

Input Schema

NameRequiredDescriptionDefault
scoresNoOPTIONAL, and each pillar inside it is optional. The four AI BVF pillars, each an honest 0–100 self-assessment, combining deterministically into the verdict: governance_risk ≥ 70 OR financial_return ≤ 20 returns Stop; strategic_alignment, financial_return and change_enablement all ≥ 60 with governance_risk ≤ 40 returns Accelerate; everything else returns Fix. Pass ONLY the pillars the user has real evidence for — do NOT invent numbers for the rest. Missing pillars are estimated deterministically by the engine from disclosed AI BVF planning assumptions, the response reports which via pillar_basis and scores_used, decision score is haircut by how much was estimated, and a fully-estimated pass can never return Accelerate (it returns Fix pending confirmation). So call immediately with whatever the user gave you, then ask for evidence on the estimated pillars and re-call to firm the verdict up.
ai_tierYesAmbition of the AI being deployed: gen1 = automation/RPA, gen2 = GenAI, gen3 = agentic. Interacts with readiness — a more ambitious tier running on lower readiness widens the pace-layer gap, which discounts the modelled EUR value even when the four pillar scores are strong.
functionYesBusiness function where the AI will operate, as one of the accepted enum values — selects which benchmark value drivers and rate ranges apply. Call list_taxonomy for the exact strings if unsure.
industryYesYour industry, as one of the accepted enum values — used to select the benchmark rate multiplier applied to the modelled EUR value. Call list_taxonomy for the exact strings if unsure.
readinessYesOrganisational readiness, honest self-assessment: agile = cross-functional, fast decisions; traditional = functional hierarchy; siloed = rigid, hand-off heavy. Sets the value-capture rate and, paired with ai_tier, the pace-layer drag — lower readiness against a higher tier reduces the captured value. Self-report is gameable: when the user has real process numbers, call infer_readiness first and pass its measured classification here instead.
revenue_eurYesApproximate annual revenue in EUR (must be ≥ 0). Scales the whole output: the disclosed AI BVF planning rates are applied as fractions of this figure, so the modelled EUR value range grows with it. A rough order-of-magnitude estimate is fine.
work_architectureNoEvidence that workflows, roles, decision rights and measures are ready. Pass only what is known. Explicit gaps and omitted checks block Accelerate until all four checks are evidenced.
signal_completenessNoOptional 0 to 1 input-quality factor. The default ranges from 0.5 when all pillars are estimated to 1 when all are supplied. Supplied values still require evidence review. Lower this factor when the supplied pillars rest on weak evidence.

Output Schema

NameRequiredDescriptionDefault
auditNoReproducibility record: engine version, the rules that fired, and the resolved inputs. Deterministic, no timestamps. If the verdict is challenged months later, the same inputs on the same engine version reproduce it exactly.
caveatNoPresent only when signal_completeness was low: warns the verdict rests on soft inputs and confidence was reduced.
reasonYesOne-line justification for the classification.
driversYesNamed value drivers behind the estimate.
feedbackNoOptional three-question feedback route, present only for Fix/Stop verdicts. The page records the response anonymously only when the user chooses an answer; no assessment data is attached.
bvf_versionYesAI BVF protocol version used.
multipliersYesFactors applied to the base rates.
scores_usedNoThe four pillar values the verdict was actually computed on, whether given by the caller or estimated by the engine. Show these to the user when any pillar was estimated.
sensitivityNoWhat moves this verdict, computed deterministically: the value if readiness were one notch worse, the value at revenue minus 20 percent, and the nearest single-pillar movements that flip the classification. Boards trust ranges with visible assumptions over point estimates; show this.
pillar_basisNoPer pillar: "given" (caller supplied it) or "estimated" (deterministic prior). When any pillar is estimated, tell the user which, and ask for evidence on those to firm up the verdict.
net_value_eurYesReadiness-adjusted benefit hypothesis before project build, run and change costs. Replace planning rates with scoped economics before funding.
classificationYesThe verdict for this initiative.
interpretationNoMeaning and limits of compatibility fields. Present these labels when explaining the result.
applied_modulesYesScoring-rule and sector-context labels. Sector labels do not certify clinical validation or regulatory compliance.
gross_value_eurYesModelled gross value in EUR before capture, low/high.
benchmark_sourceYesProvenance and evidence status for the AI BVF planning rates applied.
work_architectureYesThe work architecture gate across workflow, roles, human decision rights and performance measures. A stated gap or missing evidence blocks Accelerate.
advisory_next_stepNoOptional CTA, present only for Fix/Stop verdicts.
decision_confidenceYesHeuristic decision score, 0 to 100, adjusted for input quality. This score has no probability calibration.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed26 schema fields changedv0.14.14
    • changedInput schema / properties / ai_tier / description
      Previous value: -"gen1=automation/RPA, gen2=GenAI, gen3=agentic."New value: +"Ambition of the AI being deployed: gen1 = automation/RPA, gen2 = GenAI, gen3 = agentic. Interacts with readiness — a more ambitious tier running on lower readiness widens the pace-layer gap, which discounts the modelled EUR value even when the four pillar scores are strong."
    • changedInput schema / properties / function / description
      Previous value: -"Business function where the AI will operate."New value: +"Business function where the AI will operate, as one of the accepted enum values — selects which benchmark value drivers and rate ranges apply. Call list_taxonomy for the exact strings if unsure."
    • changedInput schema / properties / industry / description
      Previous value: -"Your industry. See list_taxonomy if unsure."New value: +"Your industry, as one of the accepted enum values — used to select the benchmark rate multiplier applied to the modelled EUR value. Call list_taxonomy for the exact strings if unsure."
    • changedInput schema / properties / readiness / description
      Previous value: -"Organisational readiness. Honest self-assessment."New value: +"Organisational readiness, honest self-assessment: agile = cross-functional, fast decisions; traditional = functional hierarchy; siloed = rigid, hand-off heavy. Sets the value-capture rate and, paired with ai_tier, the pace-layer drag — lower readiness against a higher tier reduces the captured value. Self-report is gameable: when the user has real process numbers, call infer_readiness first and pass its measured classification here instead."
    • changedInput schema / properties / revenue_eur / description
      Previous value: -"Approximate annual revenue in EUR."New value: +"Approximate annual revenue in EUR (must be ≥ 0). Scales the whole output: the disclosed AI BVF planning rates are applied as fractions of this figure, so the modelled EUR value range grows with it. A rough order-of-magnitude estimate is fine."
    • addedInput schema / properties / scores / description
      Added value: +"OPTIONAL, and each pillar inside it is optional. The four AI BVF pillars, each an honest 0–100 self-assessment, combining deterministically into the verdict: governance_risk ≥ 70 OR financial_return ≤ 20 returns Stop; strategic_alignment, financial_return and change_enablement all ≥ 60 with governance_risk ≤ 40 returns Accelerate; everything else returns Fix. Pass ONLY the pillars the user has real evidence for — do NOT invent numbers for the rest. Missing pillars are estimated deterministically by the engine from disclosed AI BVF planning assumptions, the response reports which via pillar_basis and scores_used, decision score is haircut by how much was estimated, and a fully-estimated pass can never return Accelerate (it returns Fix pending confirmation). So call immediately with whatever the user gave you, then ask for evidence on the estimated pillars and re-call to firm the verdict up."
    • changedInput schema / properties / scores / properties / change_enablement / description
      Previous value: -"Sponsor, owner, funded change budget (0-100)."New value: +"Optional; when omitted, estimated from readiness (agile 55, traditional 45, siloed 32 — always below the 60 floor, because an unevidenced change capability is unproven). Sponsor in place, owner named, change budget funded (0–100, higher is better). Must be ≥ 60 for an Accelerate verdict."
    • changedInput schema / properties / scores / properties / financial_return / description
      Previous value: -"Strength of modelled return (0-100)."New value: +"Optional; when omitted, estimated from the disclosed AI BVF planning range for the function (40–52, never enough to clear 60 unmodelled, never low enough to force a Stop). Strength of the modelled return (0–100, higher is better). A value ≤ 20 forces a Stop on its own; ≥ 60 is one of the four conditions required for Accelerate."
    • changedInput schema / properties / scores / properties / governance_risk / description
      Previous value: -"Regulatory / reputational exposure. Higher = more risk (0-100)."New value: +"Optional; when omitted, estimated from tier and regulated context (gen1 30 / gen2 42 / gen3 55, +10 in a regulated function, +8 in a regulated industry — agentic AI in regulated finance estimates at 73 and forces a Stop until governance evidence exists). This pillar is INVERTED: higher means MORE risk. ≥ 70 forces a Stop on its own; must be ≤ 40 for Accelerate."
    • changedInput schema / properties / scores / properties / strategic_alignment / description
      Previous value: -"How clearly this moves a board-level KPI (0-100)."New value: +"Optional; estimated at 50 (unproven) when omitted, since alignment to a board KPI cannot be read from context. How clearly this moves a board-level KPI (0–100, higher is better). Must be ≥ 60 — together with financial_return ≥ 60, change_enablement ≥ 60 and governance_risk ≤ 40 — for an Accelerate verdict."
    • removedInput schema / properties / scores / required
      Removed value: -[
      -  "strategic_alignment",
      -  "financial_return",
      -  "change_enablement",
      -  "governance_risk"
      -]
    • changedInput schema / properties / signal_completeness / description
      Previous value: -"Optional 0–1. How grounded the four pillar scores are in real evidence versus estimated from context. Defaults to 1 (treated as measured). If the organisation lacks formal change-readiness or risk metadata, estimate the pillars from what you know AND set this lower to say so — decision confidence is reduced proportionally and a caveat is attached, instead of returning a falsely confident verdict on soft inputs."New value: +"Optional 0 to 1 input-quality factor. The default ranges from 0.5 when all pillars are estimated to 1 when all are supplied. Supplied values still require evidence review. Lower this factor when the supplied pillars rest on weak evidence."
    • addedInput schema / properties / work_architecture
      Added value: +{
      +  "description": "Evidence that workflows, roles, decision rights and measures are ready. Pass only what is known. Explicit gaps and omitted checks block Accelerate until all four checks are evidenced.",
      +  "properties": {
      +    "decision_rights_defined": {
      +      "description": "True only when decision, override and escalation rights have named human owners, false when authority remains unclear.",
      +      "type": "boolean"
      +    },
      +    "measures_updated": {
      +      "description": "True only when performance measures and incentives reflect the redesigned work, false when the old measures remain.",
      +      "type": "boolean"
      +    },
      +    "roles_redesigned": {
      +      "description": "True only when affected roles, accountabilities and capability expectations have been rewritten, false when roles remain unchanged.",
      +      "type": "boolean"
      +    },
      +    "workflow_redesigned": {
      +      "description": "True only when the end-to-end workflow has been redesigned around the AI and retained human judgement, false when the existing workflow remains.",
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "industry",
      -  "revenue_eur",
      -  "function",
      -  "ai_tier",
      -  "readiness",
      -  "scores"
      -]New value: +[
      +  "industry",
      +  "revenue_eur",
      +  "function",
      +  "ai_tier",
      +  "readiness"
      +]
    • changedOutput schema / properties / applied_modules / description
      Previous value: -"BVF scoring modules that fired for this input."New value: +"Scoring-rule and sector-context labels. Sector labels do not certify clinical validation or regulatory compliance."
    • addedOutput schema / properties / audit
      Added value: +{
      +  "description": "Reproducibility record: engine version, the rules that fired, and the resolved inputs. Deterministic, no timestamps. If the verdict is challenged months later, the same inputs on the same engine version reproduce it exactly.",
      +  "properties": {
      +    "bvf_version": {
      +      "type": "string"
      +    },
      +    "engine": {
      +      "type": "string"
      +    },
      +    "engine_version": {
      +      "type": "string"
      +    },
      +    "inputs_used": {
      +      "description": "The resolved inputs the result was computed on, including estimated pillar values.",
      +      "type": "object"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "rules_fired": {
      +      "description": "The rules that actually fired, in order: estimation, gates, classification, value arithmetic.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • changedOutput schema / properties / benchmark_source / description
      Previous value: -"Citation for the benchmark rates applied."New value: +"Provenance and evidence status for the AI BVF planning rates applied."
    • changedOutput schema / properties / decision_confidence / description
      Previous value: -"Confidence in the verdict, 0-100."New value: +"Heuristic decision score, 0 to 100, adjusted for input quality. This score has no probability calibration."
    • addedOutput schema / properties / feedback
      Added value: +{
      +  "description": "Optional three-question feedback route, present only for Fix/Stop verdicts. The page records the response anonymously only when the user chooses an answer; no assessment data is attached.",
      +  "properties": {
      +    "question": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "format": "uri",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "question",
      +    "url"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / interpretation
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "description": "Meaning and limits of compatibility fields. Present these labels when explaining the result.",
      +  "type": "object"
      +}
    • changedOutput schema / properties / net_value_eur / description
      Previous value: -"Modelled net value in EUR after capture rate, low/high."New value: +"Readiness-adjusted benefit hypothesis before project build, run and change costs. Replace planning rates with scoped economics before funding."
    • addedOutput schema / properties / pillar_basis
      Added value: +{
      +  "description": "Per pillar: \"given\" (caller supplied it) or \"estimated\" (deterministic prior). When any pillar is estimated, tell the user which, and ask for evidence on those to firm up the verdict.",
      +  "properties": {
      +    "change_enablement": {
      +      "enum": [
      +        "given",
      +        "estimated"
      +      ],
      +      "type": "string"
      +    },
      +    "financial_return": {
      +      "enum": [
      +        "given",
      +        "estimated"
      +      ],
      +      "type": "string"
      +    },
      +    "governance_risk": {
      +      "enum": [
      +        "given",
      +        "estimated"
      +      ],
      +      "type": "string"
      +    },
      +    "strategic_alignment": {
      +      "enum": [
      +        "given",
      +        "estimated"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / scores_used
      Added value: +{
      +  "description": "The four pillar values the verdict was actually computed on, whether given by the caller or estimated by the engine. Show these to the user when any pillar was estimated.",
      +  "properties": {
      +    "change_enablement": {
      +      "type": "number"
      +    },
      +    "financial_return": {
      +      "type": "number"
      +    },
      +    "governance_risk": {
      +      "type": "number"
      +    },
      +    "strategic_alignment": {
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / sensitivity
      Added value: +{
      +  "description": "What moves this verdict, computed deterministically: the value if readiness were one notch worse, the value at revenue minus 20 percent, and the nearest single-pillar movements that flip the classification. Boards trust ranges with visible assumptions over point estimates; show this.",
      +  "properties": {
      +    "readiness_one_notch_down": {
      +      "description": "Null when readiness is already siloed.",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "revenue_minus_20pct": {
      +      "type": "object"
      +    },
      +    "verdict_flips": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / work_architecture
      Added value: +{
      +  "description": "The work architecture gate across workflow, roles, human decision rights and performance measures. A stated gap or missing evidence blocks Accelerate.",
      +  "properties": {
      +    "blocks_accelerate": {
      +      "type": "boolean"
      +    },
      +    "checks": {
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "gaps": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "gate": {
      +      "type": "string"
      +    },
      +    "next_question": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "enum": [
      +        "unknown",
      +        "partial",
      +        "gap",
      +        "ready"
      +      ],
      +      "type": "string"
      +    },
      +    "unknowns": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "status",
      +    "blocks_accelerate",
      +    "checks",
      +    "gaps",
      +    "unknowns",
      +    "gate"
      +  ],
      +  "type": "object"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "bvf_version",
      -  "classification",
      -  "reason",
      -  "net_value_eur",
      -  "gross_value_eur",
      -  "decision_confidence",
      -  "multipliers",
      -  "drivers",
      -  "benchmark_source",
      -  "applied_modules"
      -]New value: +[
      +  "bvf_version",
      +  "classification",
      +  "reason",
      +  "net_value_eur",
      +  "gross_value_eur",
      +  "decision_confidence",
      +  "multipliers",
      +  "drivers",
      +  "benchmark_source",
      +  "applied_modules",
      +  "work_architecture"
      +]
  2. Changed2 schema fields changedv0.6.0
    • addedInput schema / properties / signal_completeness
      Added value: +{
      +  "description": "Optional 0–1. How grounded the four pillar scores are in real evidence versus estimated from context. Defaults to 1 (treated as measured). If the organisation lacks formal change-readiness or risk metadata, estimate the pillars from what you know AND set this lower to say so — decision confidence is reduced proportionally and a caveat is attached, instead of returning a falsely confident verdict on soft inputs.",
      +  "maximum": 1,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedOutput schema / properties / caveat
      Added value: +{
      +  "description": "Present only when signal_completeness was low: warns the verdict rests on soft inputs and confidence was reduced.",
      +  "type": "string"
      +}
  3. Changed1 schema field changedv0.5.0
    • changedOutput schema / properties / decision_confidence / description
      Previous value: -"Confidence in the verdict, 0–1."New value: +"Confidence in the verdict, 0-100."
  4. Changed1 schema field changedv0.4.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "advisory_next_step": {
      +      "description": "Optional CTA, present only for Fix/Stop verdicts.",
      +      "type": "string"
      +    },
      +    "applied_modules": {
      +      "description": "BVF scoring modules that fired for this input.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "benchmark_source": {
      +      "description": "Citation for the benchmark rates applied.",
      +      "type": "string"
      +    },
      +    "bvf_version": {
      +      "description": "AI BVF protocol version used.",
      +      "type": "string"
      +    },
      +    "classification": {
      +      "description": "The verdict for this initiative.",
      +      "enum": [
      +        "Accelerate",
      +        "Fix",
      +        "Stop"
      +      ],
      +      "type": "string"
      +    },
      +    "decision_confidence": {
      +      "description": "Confidence in the verdict, 0–1.",
      +      "type": "number"
      +    },
      +    "drivers": {
      +      "description": "Named value drivers behind the estimate.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "gross_value_eur": {
      +      "description": "Modelled gross value in EUR before capture, low/high.",
      +      "properties": {
      +        "high": {
      +          "type": "number"
      +        },
      +        "low": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "low",
      +        "high"
      +      ],
      +      "type": "object"
      +    },
      +    "multipliers": {
      +      "description": "Factors applied to the base rates.",
      +      "properties": {
      +        "capture_high": {
      +          "type": "number"
      +        },
      +        "capture_low": {
      +          "type": "number"
      +        },
      +        "industry": {
      +          "type": "number"
      +        },
      +        "tier": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "industry",
      +        "tier",
      +        "capture_low",
      +        "capture_high"
      +      ],
      +      "type": "object"
      +    },
      +    "net_value_eur": {
      +      "description": "Modelled net value in EUR after capture rate, low/high.",
      +      "properties": {
      +        "high": {
      +          "type": "number"
      +        },
      +        "low": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "low",
      +        "high"
      +      ],
      +      "type": "object"
      +    },
      +    "reason": {
      +      "description": "One-line justification for the classification.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "bvf_version",
      +    "classification",
      +    "reason",
      +    "net_value_eur",
      +    "gross_value_eur",
      +    "decision_confidence",
      +    "multipliers",
      +    "drivers",
      +    "benchmark_source",
      +    "applied_modules"
      +  ],
      +  "type": "object"
      +}
  5. First observedv0.3.5

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent/non-destructive; the description adds substantially more: deterministic calculation with no authentication, anonymous telemetry with an AIBVF_TELEMETRY_DISABLE=1 opt-out, estimation behavior for missing pillars (reported via pillar_basis, decision score haircut, fully-estimated pass can never return Accelerate), and the returned artifacts. This is exactly the kind of context that goes beyond structured hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and the CALL THIS trigger, then alternatives, then return values and behavioral notes. It is dense and somewhat long, repeating pillar/estimation logic that the schema also covers, but nearly every sentence carries routing or behavioral information, so it is appropriately sized for a complex 8-param tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a high-complexity tool with nested objects, four enums, and a rich output schema, the description covers the trigger, the alternatives, the estimation fallback, the verdict logic, and the trust/telemetry model. Nothing an agent needs to call it correctly is missing; return details it summarizes are already backed by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema is extremely rich (enum meanings, pillar thresholds), so the baseline is 3. The description adds genuine operational meaning on top: pass only pillars with real evidence, call immediately with partial data then re-call as evidence arrives, and the verdict-combination logic. It does not add per-parameter syntax beyond the schema, so it lands just above the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb+resource: "Canonical-field scorer for one AI initiative," and distinguishes itself from siblings by name (assess_ai_initiative, score_portfolio, diagnose_process). An agent can tell exactly what this tool produces (a verdict plus benefit ranges) versus the alternatives without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ("CALL THIS when industry, revenue_eur, function, ai_tier and readiness are already known, or when re-scoring with measured pillar evidence") and routes away to alternatives: assess_ai_initiative for ordinary business language, score_portfolio for several initiatives, diagnose_process for measured waste, infer_readiness when process numbers exist. When/when-not/alternatives are all present.

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