add_custom_pattern

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

The description discloses the mutation target (data/patterns-custom.json) and that it is available for all projects, plus a lifecycle hint. However, it does not reveal potential side effects like overwriting, error handling, or permissions, and no annotations are provided.

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?

One sentence, front-loaded with the action, and includes the essential file location and lifecycle guidance without unnecessary words.

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 description is adequate for a simple add operation: it covers purpose, destination, and availability. However, missing parameter schema details and behavioral edge cases prevent it from being fully complete.

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 schema only declares a single object parameter with no descriptions, and the description does not elaborate on required fields or structure of the pattern object. The phrase 'patrón agéntico descubierto por un agente' provides only a general notion, not parameter semantics.

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 tool adds an agent-discovered pattern to data/patterns-custom.json, using a specific verb and resource. It distinguishes from sibling read/removal tools by mentioning the file destination and pattern type.

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?

It provides context that patterns are agent-discovered and stored in the custom file, with promotion to patterns.py when mature. However, it does not explicitly name alternative tools or state when not to use it.

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