Set Forms page conditions operator

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

Annotations already declare readOnly=false, idempotent=true, destructive=false, and openWorld=true, so the safety and mutation profile is covered. The description only adds "returns the envelope," which is thin context; it does not explain what preconditions the page must satisfy (e.g., existing condition groups) before the operator can be set.

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 clause that front-loads the action and the affected object, with the return note appended. No padding or redundancy.

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 simple three-parameter idempotent setter with rich annotations and full schema coverage, this is nearly sufficient. The only shortfall is the lack of routing guidance among the four similarly named operator tools, which a complete definition should address.

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 coverage is 100%, so page_id, operator, and survey_id are already documented, including the and/or values. The description's "BETWEEN a page's condition groups" marginally clarifies operator scope but adds no format or constraint detail beyond the schema, so 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?

Specific verb ("Set") plus precise resource: the boolean operator joining a page's condition groups. This clearly differentiates it from forms_conditions_page_update (which edits the conditions themselves) and from the question/submit/hook operator siblings, though no sibling is named explicitly.

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 guidance on when to use this versus forms_conditions_page_update, forms_conditions_question_update_operator, forms_conditions_submit_update_operator, or forms_conditions_hook_update_operator. The agent must infer context from the name alone.

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