RC Engine

copy_critique

Read-onlyIdempotent

Evaluate generated copy against conversion heuristics. Score it across seven categories to decide whether to ship, revise, or rewrite.

Instructions

Self-critique the generated copy system against conversion heuristics. Scores across 7 categories: Clarity (25%), Persuasion Framework (20%), Behavioral Design (15%), Voice & Tone (15%), Microcopy (10%), Specificity (10%), SEO (5%). Returns weighted score with verdict: SHIP (4.0+), REVISE (3.0-3.9), or REWRITE (<3.0). Call AFTER copy_generate. Loads the COPY-SYSTEM.md artifact automatically.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_path": "<project_path>"
    },
    "name": "copy_critique"
  }
}

Input Schema

Name	Required	Description	Default
`project_path`	Yes	Absolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety. The description adds valuable behavioral context beyond annotations: the automatic loading of COPY-SYSTEM.md and the detailed weighted scoring with verdicts, which enhances transparency.

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

Conciseness5/5

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

The description is concise and well-structured: a one-sentence purpose explanation, a detailed list of scoring categories, and a final sentence covering usage order and verdicts. No wasted words, all information is relevant.

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

Completeness4/5

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

Given the tool's moderate complexity (one param, no output schema), the description is quite complete: it covers purpose, scoring methodology, verdict thresholds, usage sequencing, and artifact loading. Minor gaps include how to interpret the score in practice and a more explicit link between project_path and the artifact.

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

Parameters3/5

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

The input schema has 100% coverage for the single parameter project_path, so baseline is 3. The description indirectly suggests project_path is used to locate COPY-SYSTEM.md, but it does not explicitly elaborate on parameter semantics beyond the schema.

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?

The description clearly states the tool's function: 'Self-critique the generated copy system against conversion heuristics.' It provides specific details on the 7 scoring categories and verdict thresholds, making it distinct from sibling tools like copy_generate and copy_iterate.

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

Usage Guidelines4/5

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

The description explicitly instructs 'Call AFTER copy_generate,' providing a clear usage sequence. However, it lacks any when-not-to-use guidance or explicit alternatives, which would elevate it to a 5.

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