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

With no annotations present, the description carries the full behavioral burden and leaves the important questions open. It says 'sanitizes' but never states whether the payload is mutated in place or a cleaned copy is returned, whether failures raise an error or return a violation report, or that sanitization may rewrite the caller's copy. 'Validates' and 'sanitizes' are also two different behaviors bundled into one verb phrase without explaining their relationship.

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?

A single front-loaded sentence with no filler, and the gate list is efficiently enumerated. It loses a point because GATE-10/11/12 and 'AI slop' are unexplained internal jargon that the reader must already know.

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?

For a validating/sanitizing tool with no annotations and no output schema, the description should at minimum sketch the return shape (pass/fail, list of violations, sanitized payload) and the effect of sanitization. Neither is present, so an agent cannot predict the outcome of a call or know how to interpret it.

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 description coverage is 100% and all three parameters (jsonPayload, json_payload, voice_archetype_id) are documented in the schema itself, so the baseline of 3 applies. The description adds nothing about what voice_archetype_id changes about validation, which is the one genuinely under-specified parameter.

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?

States a specific verb pair (validates and sanitizes) plus a specific resource (copy manifest) and enumerates the exact rule sets enforced (GATE-10 jargon ban, GATE-11 slop/Unicode star ban, GATE-12 repetitive sentence ban). None of the sibling tools (billing, agent key, radar, page draft) overlap with this gate-checking function, so an agent can select it unambiguously.

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?

Usage is only implied: naming editorial gates signals this is a pre-publish quality check on copy manifests, but the description never says when to call it, whether it should run before or after drafting, or what to do with a failing result. No alternatives or exclusions are offered, though no sibling is a plausible substitute.

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