Delete Forms submit-button show condition

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds one genuinely useful behavioral fact beyond the annotations: the deletion is scoped and leaves other condition groups intact. It says nothing about reversibility, required permissions, or failure behavior for an invalid condition_id.

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 with zero filler; the destructive action and its scope bound are both stated immediately.

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 two-parameter destructive delete, the description plus annotations and a fully documented schema cover what an agent needs to invoke it correctly. Minor gaps remain around failure modes and whether the group's operator/child conditions are also removed.

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%, with both survey_id and condition_id documented inline including where to source them (surveys_list, the matching *_list tool). The description adds no parameter detail, 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 ('Delete') and resource ('one condition group from the submit button'), and the scope note ('the other groups stay untouched') makes it clear this targets the submit-button condition set rather than the question/page/hook condition sets. It does not explicitly name those sibling tools, so it stops short of a 5.

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?

There is no guidance on when to use this versus forms_conditions_submit_update, forms_conditions_submit_set_operator, or the analogous question/page/hook delete tools, and no prerequisites or exclusions are given. Usage is only implied by the tool name.

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