remove_custom_pattern

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

With no annotations, the description carries the full burden. It discloses that it modifies a file, implying a destructive deletion, but does not state whether the operation is irreversible, what happens if the pattern does not exist, or any side effects. Given this is a mutation tool, more behavioral disclosure is needed.

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, focused sentence that is front-loaded and free of redundancy. Every word earns its place, achieving maximum efficiency.

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?

The tool is simple with one parameter and no output schema, so minimal context is acceptable. The description names the target file, giving some context. However, it lacks behavior on error cases or return values, leaving gaps for an agent using 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 0%, so the description must compensate. It implies the 'name' parameter is the identifier of the pattern to remove, but does not clarify case sensitivity, exact naming conventions, or whether the full filename is expected. Minimal added value 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?

The description clearly states the action ('Elimina' = removes) and the resource ('un patrón custom') with a specific file location ('data/patterns-custom.json'). It distinguishes from siblings like remove_custom_preset (different resource) and add_custom_pattern (opposite operation).

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. It does not mention that it is specifically for patterns and not presets, nor does it explain any prerequisites or conditions. The description is purely definitional with no contextual usage notes.

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