Modify Forms integration-group condition

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and repeatability profile is covered. The description does add real value by warning that this is a FULL replacement, meaning clauses omitted from the body are dropped — a consequence not visible from the annotations. It does not, however, describe the response or error behavior.

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?

A single sentence, front-loaded with the action and resource, with the critical caveat ('a FULL replacement') placed where it cannot be missed. 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 nested-body mutation with no output schema and a genuinely destructive-to-existing-data semantic, the description conveys the replacement behavior but says nothing about what the call returns, permission requirements, or what happens on a malformed group. The rich input schema and annotations carry most of the load, leaving this adequate but thin.

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% and the nested body schema is unusually well documented (clause types, operators, the 100-char value cap, the absence of a per-clause operator). The description adds no parameter-level detail beyond what the schema already provides, so the baseline 3 applies.

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 (Replace) and resource (an integration group's condition group), and the 'FULL replacement' qualifier distinguishes it from the sibling forms_conditions_hook_set_operator, which only touches the operator. It stops short of explicitly naming that sibling, so differentiation is implied rather than spelled out.

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 'FULL replacement' framing implies when this is appropriate (rewriting an entire condition group) versus a narrower update, but no alternative is named and no prerequisites or exclusions are given. Usage is inferable from the emphasis rather than stated.

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