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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a mutating, potentially destructive call. The description adds real value by disclosing patch semantics (only supplied fields change), but it does not mention permissions, reversibility, or the effect of flipping a level from 'should' to 'must'.

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?

Two short sentences, front-loaded with the action and immediately followed by the most decision-relevant behavior. No filler.

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?

For a small mutation tool with complete schema and annotations covering the safety profile, the description is adequate but thin; it omits any note on what happens to omitted fields beyond the patch hint, error behavior for an unknown id, and whether the change is reversible.

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 100%, including a detailed enum explanation for level, so the schema carries the parameter burden and the baseline is 3. The patch-semantics sentence complements the schema by explaining that id is the only required field and others are optional, but adds no syntax or constraint detail beyond it.

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?

States a specific verb (Edit) and resource (rule) plus the two mutable fields (text, level), which cleanly separates it from create_rule and delete_rule. It does not explicitly contrast with the other update_* siblings, but the resource is unambiguous.

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?

"Only supplied fields change" is genuinely useful usage context for a partial-update call, but there is no guidance on when to reach for this versus create_rule/delete_rule or on prerequisites such as the rule needing to exist.

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