Create Forms page show condition

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

Annotations already declare readOnly=false, destructive=false and idempotent=false, so the safety profile is covered. The description adds value beyond them by disclosing the return value ('the created group with its server-assigned integer id') and the semantic effect on page visibility, which the annotations cannot convey.

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 sentences with the core effect (page shows only when conditions match) front-loaded, followed by one useful constraint and the return value. No filler, and the break before the return sentence aids scanning.

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 non-idempotent mutation with no output schema, the description covers the essential gaps: what it creates, its visibility effect, and the shape of the response. It omits error/conflict behavior and any interaction with the existing operator, but nothing critical to a correct call is missing.

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% and the nested clause object is thoroughly documented, so the baseline is 3. The note that clauses reference question slugs repeats what the schema already states for the 'question' field, adding only marginal reinforcement rather than new meaning.

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?

The description names a specific verb (add) and resource (condition group on a page) and adds real semantics — 'the page shows only when its conditions match.' The 'page' scope implicitly separates it from the sibling forms_conditions_question_create, but no sibling is named explicitly, so it falls short of full routing clarity.

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 only implied: the agent can infer this is the write path for page show-conditions, but the description never states when to use it versus forms_conditions_question_create, forms_conditions_page_update, or forms_conditions_page_set_operator. No prerequisites or exclusions are given.

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