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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the bar is lower; the description adds genuine value by disclosing the partial-update semantics ("Only non-null fields are updated"), which tells the agent omitted fields survive. However, it never addresses the tension between "Replace" wording and destructiveHint, does not clarify whether the nested seliee_rules object is merged or overwritten wholesale, and mentions no permissions or reversibility.

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, no filler, with the identity/lookup information front-loaded ahead of the update-semantics clause. Every clause carries information the reader needs.

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 destructive, four-parameter mutation with 0% schema description coverage and no output schema, the description leaves the agent unable to construct a call: the contents and shape of seliee_rules are unexplained and there is no statement of what a caller can change. It answers "which rule" but not "with what changes."

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%, so the description must carry the parameter burden, yet it only explains rule_id/rule_uuid as lookup keys — and even then does not say whether one or both are required (required is empty). The two payload parameters, seliee_rules (an opaque additionalProperties object) and seliee_rule_title, are never mentioned, leaving half the parameters completely undocumented.

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?

Names a specific verb and resource ("Replace fields of an existing seliee_rule") and pins the resource down by its two lookup keys, which clearly separates it from create_rule, delete_rule, get_rule and list_rules in the sibling set. It stops short of explicitly distinguishing itself from siblings like create_rule/delete_rule, but the intent 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?

"existing ... (found by `rule_id` or `rule_uuid`)" implies the precondition that the rule must already exist, but there is no explicit when-to-use guidance and no mention of alternatives such as create_rule for new rules or get_rule to read before editing. Usage is inferable rather than stated.

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