Replace occurrences in text.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The original text | |
| search | Yes | Text to search for | |
| replacement | No | Replacement text |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes | ||
| original | Yes | ||
| occurrences_replaced | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden but only says 'Replace occurrences.' It does not disclose case sensitivity, replacement behavior for empty replacement, or whether replacement is global. This is insufficient for a mutation 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 sentence is concise and front-loaded. It is not verbose, but could be expanded slightly without losing conciseness.
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?
Given no annotations and an output schema, the description lacks essential details like whether replacement is global, case sensitivity, and behavior with missing parameters. Not complete enough for an agent to use confidently.
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%, so baseline is 3. The description adds 'occurrences' but adds no meaningful detail beyond the schema's parameter descriptions.
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 'Replace occurrences in text.' clearly states the action (replace) and the resource (text). It is specific and distinct from sibling tools like regex_replace.
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?
No guidance on when to use this tool versus alternatives like regex_replace. The description does not mention scope, such as whether it replaces all occurrences or only the first.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
