Publicar formulário

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

No annotations are provided, so the description carries full responsibility. It discloses the behavior (publish/unpublish) and adds that unpublished forms do not accept responses, explaining the practical consequence. It does not cover potential side effects or permissions, but for a simple toggle this is sufficient.

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 two sentences: the first states the core functionality, the second provides essential context about initial state. No unnecessary words or repetition, perfectly front-loaded and efficient.

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 tool with two parameters and a clear toggle behavior, the description is complete. It explains the starting state, the effect on response acceptance, and the expected use case. There is no output schema, and none is needed for this state-change operation.

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 schema covers both parameters with clear descriptions: formId is the form ID, published explains true makes it visible and accepting responses, false unpublishes. The description adds the context that forms start unpublished, which reinforces the meaning of the 'published' parameter but doesn't introduce new syntax or format details beyond the schema's high coverage.

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 clearly states the primary action: 'Publica ou despublica um formulário' (publishes or unpublishes a form), using a specific verb and resource. It distinguishes itself from sibling tools that deal with questions, sections, or responses by explicitly mentioning the publish/unpublish toggle.

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 provides useful context: forms created via API start unpublished and do not accept responses until published, implying this tool should be used after form creation to enable responses. It gives a clear 'when to use' signal, though it does not explicitly exclude alternatives or mention when not to use it.

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