Modify Forms page show condition

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

Annotations already declare idempotency, non-destructiveness and open-world behavior, but the description adds the critical semantic that this is a whole-group replacement rather than a merge — a real behavioral trait an agent needs to avoid silently dropping clauses. It stops short of stating what happens to omitted clauses or permission requirements.

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 front-loaded sentence that states the action and the one non-obvious semantic caveat with zero waste. Nothing to trim.

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 four-required-param mutation it covers the key trap (full replacement) and relies on annotations plus the 100%-covered schema for the rest. Missing details are minor: no mention of auth scope or that condition_id must reference an existing group.

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 rich nested descriptions for operator, items, type, value, question and condition, so the schema carries parameter meaning. The description adds no parameter-level detail beyond what the schema provides, which is the expected baseline.

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?

Specific verb (replace) plus resource (a page's condition group), so an agent can tell it apart from the page condition create/list/get siblings. It does not explicitly contrast with forms_conditions_page_set_operator or page_create, but the semantics are clear.

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 statement of when to use this tool versus alternatives (set_operator, page_create, page_delete). The 'FULL replacement' note implies intent but never tells the agent the precondition (an existing condition group must exist) or when to prefer set_operator instead.

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