Create Forms question show condition

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

Annotations already declare the mutation profile (readOnly=false, destructive=false, idempotent=false). The description adds genuine context beyond them: the minimum-clause constraint and the fact that the response contains a server-assigned integer id, which matters for a non-idempotent create. It stops short of describing auth requirements or rate limits.

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?

Two tight paragraphs, front-loaded with the action and its effect, followed by the two constraints that matter. No filler sentences.

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-object mutation with no output schema, the description covers the required structure constraint and the return shape (created group with integer id), which is exactly what the missing output schema would otherwise supply. Remaining gaps are minor: no permissions or error behavior noted.

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 the schema already documents operator, items, clause type/value/question/condition in detail. The description's note that operator joins clauses WITHIN the group and that at least one clause is required largely restates the body schema description, adding only marginal clarification. Baseline 3 is appropriate.

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 ('Add a condition group to a question') and immediately explains the semantic effect ('it shows only when its conditions match'). The 'question' scoping distinguishes it from the sibling forms_conditions_page/hook/submit_create tools, so an agent can route to it without opening the schema.

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?

Usage is implied by the purpose and the scoping to questions, but there is no explicit when-to-use guidance and no mention of the neighboring forms_conditions_question_update, set_operator, or list tools. The agent must infer that this is the creation entry point 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.