rule_set_phase

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

Annotations already indicate readOnly=false, idempotent=true, and destructive=false, and the description adds useful detail about null clearing the tag and making the rule core. It does not disclose potential side effects beyond tag modification, but transparency is adequate.

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 compact and information-dense, covering purpose, mechanism, null semantics, and valid values in a single sentence. No unnecessary words or redundant structure are present.

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 provides enough context to call the tool correctly: what it does, how tags are managed, what null means, and which phase values are valid. No output schema exists, but the outcome is clear from the described behavior.

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 phase parameter is well explained with valid enum values and null behavior, and rule_id is self-explanatory as an integer identifier for a rule. The description adds meaning beyond the schema, though rule_id itself lacks an explicit schema description.

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 attaches or removes a phase scope on a rule, identifies the tag-based mechanism ('phase:<X>'), and lists valid phases. It is immediately distinguishable from sibling tools by naming the specific rule-tag 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?

The description explains what the tool does and how null works, but it does not explicitly state when to prefer this over sibling phase-related tools, nor does it mention when not to use it. Usage guidance is implied rather than explicit.

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