Delete Forms question show condition

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

Annotations already declare destructiveHint=true and non-idempotent behavior, so the safety profile is covered. The description adds real value beyond them by clarifying the blast radius: only one condition group is removed and sibling groups are preserved, which an agent cannot infer from destructiveHint alone.

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 the scope constraint stated immediately; every clause earns its place with 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 simple, low-complexity destructive call with full schema coverage, the description plus annotations supply what an agent needs: the action, its destructive nature, and the partial-deletion scope. Additional context such as whether deletion is reversible or requires an unpublished survey is absent but not strictly required.

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%, so all three parameters (survey_id, question_id, condition_id) are already documented in the schema with their sources. The description adds no further meaning about parameter formats or constraints, so the baseline of 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 and resource (delete one condition group from a question) and adds the crucial scope qualifier that other groups remain untouched. It does not explicitly distinguish itself from the parallel forms_conditions_page_delete / _submit_delete / _hook_delete siblings, but the 'question' scope 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?

The description implies the operation is a targeted single-group removal, which hints at when it is appropriate versus a broader delete. It gives no explicit when-to-use guidance, no prerequisites, and does not point to forms_conditions_question_list as the source of condition_id or to set_operator for other modifications.

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