set_form_settings

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

With no annotations, the description carries the full burden, but it only says 'set' without disclosing whether values are overwritten, whether null leaves a setting unchanged, or what side effects occur. It doesn't mention permissions, reversibility, or failure 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?

The description is a single front-loaded sentence with no wasted words; every term earns its place. Its brevity is a strength even though other dimensions suffer from lack of detail.

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 mutation tool with no annotations and only 0% schema coverage, a seven-word description is insufficient to support correct invocation. It doesn't explain how the optional/null parameters behave, when to use this versus siblings, or what the output represents; the output schema covers return type but not usage context.

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?

The description maps 'quiz mode' and 'email collection' to the isQuiz and emailCollectionType parameters, but it adds no detail beyond the property names. At 0% schema coverage, it should explain null semantics and the emailCollectionType enum choices; it doesn't, and it also omits the required formId context.

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 concrete action ('set') and identifies the affected resources ('quiz mode' and 'email collection'), which clearly differentiates it from sibling tools like set_publish_settings. It doesn't explicitly call out what it is not, so it stops short of full sibling differentiation.

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 choose this tool rather than update_form_info or set_publish_settings, and no mention of prerequisites or exclusions. The only implicit signal is that it is for quiz mode/email collection settings, which is not enough to guide tool selection.

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