Create a default privacyscrubber.json in the active workspace root when missing, including templates for custom regex rules and exclusion bypass patterns.
Creates a default 'privacyscrubber.json' configuration file in the active workspace root directory if one does not exist. Includes template structures for custom regex rules and exclusion bypass patterns.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond that by naming the exact file, its location, and the fact that existing files are left untouched. It stops short of saying what the tool returns or whether the directory must already exist.
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?
Two sentences, no filler, with the file name and location front-loaded before the content description. Every clause carries information an agent needs.
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, non-destructive file-creation tool with rich annotations and no output schema, the description covers location, naming, conditional behavior, and content. The only meaningful gap is what the call returns (created path vs. an already-exists signal), which an agent might want.
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 takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description usefully clarifies that the target path is implicit (workspace root) rather than configurable.
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 and resource: creating a 'privacyscrubber.json' config file in the workspace root, with the contents it seeds (regex rule and exclusion bypass templates). It is clearly distinguishable from most siblings, though it does not explicitly contrast with create_agent_rules, the other file-creating tool in the list.
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 by the conditional 'if one does not exist', which tells the agent this is a bootstrap step. There is no explicit when-to-use framing, no mention of prerequisites (e.g., must a workspace be active?), and no guidance on alternatives such as create_agent_rules.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.