Prevention Rules

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

The annotation indicates destructiveHint=true, but the description does not elaborate on what might be destroyed or any side effects (e.g., overwriting existing rules). No additional behavior context beyond annotation.

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 a single short sentence, but it lacks critical information about parameters and behavior. It is under-specified rather than effectively concise.

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?

With two undocumented parameters, no output schema, and a destructiveHint annotation, the description fails to provide sufficient context for an agent to use the tool correctly. It does not explain what prevention rules are, how they are generated, or what the output format is.

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%. The description does not explain the two parameters (minOccurrences, outputPath) or their roles. 'minOccurrences' is vaguely implied by 'repeated mistake patterns', but no explicit semantic value added.

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 specifies a clear verb 'Generate' and resource 'prevention rules', with context 'from repeated mistake patterns'. It is distinguishable from other 'generate' sibling tools like 'generate_operator_artifact'.

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 guidelines on when to use this tool versus alternatives. No mention of when-not-to-use or related tools like 'generate_skill' or 'generate_operator_artifact'.

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