add_pii_pattern_tool

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

The description indicates an action that mutates state, but provides no details on persistence, reversibility, or side effects. Since no annotations are present, the description carries the full burden but fails to disclose important behavioral traits.

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 extremely short (one sentence) and front-loaded, but arguably too concise for a tool with two parameters and no annotations. It could be more efficient by adding necessary details without becoming verbose.

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 the lack of annotations and output schema, the description is incomplete. It does not explain the effect of adding/overriding a pattern, expected format for regex, or what happens on conflict. More context is needed for an agent to use it correctly.

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 input schema has 0% description coverage, and the tool description adds no meaning beyond the parameter names 'name' and 'regex'. It does not explain expected formats, constraints, or behavior (e.g., whether name must be unique).

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 (add or override) and the resource (PII detection pattern). It distinguishes from siblings like list_pii_patterns_tool and scrub_text_tool, but does not clarify the distinction between 'add' and 'override'.

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 is provided on when to use this tool versus alternatives, such as when a pattern already exists or when listing is needed first. The usage context is implied but not explicit.

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