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

With no annotations, the description carries the full burden. It discloses the safety-oriented behavior ('block accidental destruction') but does not explain what the classifier returns, whether it blocks execution or merely reports a verdict, how false positives are handled, or what happens on a destructive match.

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 wasted words; the core purpose and examples are immediately clear.

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 simple one-parameter classifier this is nearly sufficient, but with no annotations and no output schema, the description should clarify the return format (classification/verdict) so the agent knows how to act on the result.

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 100%, so the parameter is already documented. The description adds useful semantic examples of what the classifier detects ('rm -rf, DROP TABLE'), giving the agent concrete expectations beyond the schema's generic 'Shell command or action to validate'.

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 states a specific verb ('Classifies') and resource ('shell commands or DB queries'), plus the outcome ('block accidental destruction'). It is clearly distinct from the sibling truthgate_* tools, though it does not explicitly name or contrast them.

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 implied: validate a command before executing it to prevent destructive actions. There is no explicit when-to-use/when-not guidance or comparison to alternatives, leaving the agent to infer the workflow.

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

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

No annotations are provided, so the description carries the full behavioral burden. 'Zero-egress local DLP' is a genuinely useful disclosure (no network transmission, runs locally), but it does not say what the tool returns, how masks are represented, or whether masking is reversible/deterministic — significant gaps for a mutation-shaped tool.

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: the safety property ('Zero-egress local') and the action ('Masks ... before feeding to LLM') both land immediately. Nothing to trim.

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 one-parameter tool this is close, but with no annotations and no output schema the description should state what comes back (masked text, placeholders, mapping) so the agent knows the result is safe to forward. That return-behavior gap is the main missing piece.

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 100% with a single well-described parameter ('Raw code, log, or document text to redact'). The description adds no parameter-level detail such as size limits, encoding expectations, or multi-document handling, so it does not exceed what the schema already provides.

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 ('Masks') and concrete targets (API keys, PII, credentials) across named input types (code, .env, logs). It is clearly a redaction tool and does not overlap with the sibling tools (integrity verification, action inspection, credit upgrade), though it never explicitly contrasts itself with them.

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?

'...before feeding to LLM' implies the usage context, so an agent can infer this is a pre-flight sanitization step. However, there are no explicit when-to-use/when-not conditions, no mention of alternatives, and no statement about whether this replaces or complements truthgate_inspect_action or truthgate_verify_test_integrity.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the $0.99 cost and that it returns a link, but does not clarify whether calling it initiates a purchase, what permissions are required, how the link is scoped, or what side effects occur.

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 description is a single compact sentence with the core action and cost front-loaded. The promotional slash phrasing ('Pro Credit Pack / License Key link') mildly blurs exactly what is returned, but overall it is efficient.

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 zero-parameter tool this is adequate: it states the cost, the returned link, and the high-level benefit. However, with no annotations or output schema, it should clarify whether the call is purely a read/link retrieval or a purchase trigger, and what authentication or team context is needed.

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?

The tool has zero parameters and an empty schema, so there are no parameter semantics to document. The baseline score for this case is 4.

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 uses a specific verb ('Get') and resource ('Pro Credit Pack / License Key link') and states the intended outcome of unlocking audit-log and guardrail features. It is clearly distinct from the sibling tools, which focus on masking, integrity verification, and action inspection, though it does not explicitly name those alternatives.

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?

The description implies the tool is for upgrading to Pro, but gives no explicit guidance on when to use it versus alternatives, when not to use it, or what prerequisites must be met. An agent must infer the usage context entirely.

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

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

No annotations are provided, so the description carries the full disclosure burden. It names the two failure modes it detects, which is real behavioral content, but says nothing about whether the check is read-only, whether it blocks or only reports, or what verdict/response the agent receives — critical for a gate-style tool.

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 distinctive anti-pattern label comes first. It is arguably over-compressed given how little guidance surrounds it, but nothing in it is wasted.

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?

With no output schema and no annotations, the description must convey the result shape (pass/fail verdict, findings) and the calling context; it conveys neither. For a gate the agent is expected to act on, this leaves the agent unable to interpret or act on the response.

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 100%, with both parameters documented as 'test file contents', so the baseline is 3. The description reinforces the comparison semantics ('proposed edits' vs. implicitly original) but adds no format, size, or framing requirements beyond the schema.

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?

Specific verb+resource: 'Checks if proposed edits weaken test assertions or inject fake mocks' on a test-integrity target. The framing ('Anti-Silent-Fake-Success') plus the concrete detection criteria distinguish it from siblings like truthgate_inspect_action and truthgate_mask_context. It stops short of a full 5 because it never explicitly says it compares original vs. modified test files, though the schema implies that.

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?

The 'Anti-Silent-Fake-Success' label implies the trigger condition — call this before accepting edits that touch test files — but that is inferred, not stated. There is no explicit when-to-use, when-not-to-use, or comparison to the sibling tools.

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