Get Forms submit-button show condition

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds that the returned group exposes its 'operator and clauses', which is modest but useful context given there is no output schema. It does not mention auth requirements or error behavior.

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 sentence, front-loaded with the resource and its id-scoping, with no filler. Every clause earns its place.

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 two-parameter read tool whose annotations cover safety and whose schema fully documents inputs, the description is nearly sufficient, and it partially compensates for the absent output schema by naming the returned fields. A brief note on what a 'clause' contains would make it fully complete.

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% — both survey_id (24-char hex, from surveys_list) and condition_id (integer, from the matching *_list tool) are fully documented in the schema. The description adds no parameter detail beyond what the schema provides, 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 (get) and resource (one condition group of the submit button, by id), and the 'submit button' qualifier distinguishes it from the question/page/hook condition getters. It does not name the sibling list tool it complements, but the 'one ... by id' framing implies the distinction.

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 by 'by id' — the agent infers it needs a known condition_id, and the schema confirms the id comes from a *_list tool. There is no explicit when-to-use statement, no exclusion, and no named alternative (e.g. forms_conditions_submit_list) for enumerating conditions.

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