assess_qa_maturity

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

With no annotations, the description carries the full burden and does so thoroughly: it discloses determinism/no-LLM, the indicative_tmmi_level cap at 3 with the TMMi no-skip rationale, the branch behavior for AI/ML mentions including negated ones, keyword-detection limits, and non-English handling. The three distinct status outcomes (ok, insufficient_content, not_a_qa_description) are spelled out precisely.

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?

The core purpose is front-loaded and every sentence carries substantive information about a non-obvious edge case, so the length is defensible. The structure is a single dense paragraph with heavy parenthetical nesting, which makes the branch conditions harder to scan than they need to be.

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?

Despite having no output schema, the description enumerates the full return shape (status, indicative_tmmi_level, both dimension score dicts, notes, findings, disclaimer, caveats, stats, kb_version) and explains the semantics of the conditional fields. An agent has everything needed to call it and interpret the result without guessing.

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 coverage is 0% and the single parameter has no schema description, so the description must compensate — and it does: it defines what project_description should contain, the ~200-character minimum after stripping AI-disclosure boilerplate, the vocabulary requirement that separates a valid input from a recipe or meeting notes, and the language constraint that flips score_reliable.

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 leads with a specific verb+resource: deterministically assess QA process maturity from a free-text project/process description, naming the exact scope (10 TMMi process areas, Level 2 Managed + Level 3 Defined). It explicitly distinguishes itself from the sibling tools by framing the output as findings the caller must narrate themselves, versus review/estimate tools.

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?

It clearly states the valid input context (a free-text project/process description or a pasted Test Strategy/Risk Register) and the conditions under which it does not apply (under ~200 characters, no QA vocabulary). It does not, however, explicitly compare itself to siblings like review_qa_document or estimate_qa_effort, leaving the agent to infer which to choose.

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