Criar formulário

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains the default publication behavior, the draft option, and the fact that the response reports the actual publication state. This adds valuable insight beyond the basic creation action, though it does not cover permissions or error scenarios.

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 three concise sentences with no filler. It front-loads the primary action and efficiently adds key behavioral details, making it easy to parse.

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?

Given no output schema, the description adequately explains the return values (ID, edit link, response link) and the publication state. The tool is simple (3 params, no nested objects), and the description covers the essential aspects without leaving critical gaps.

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 input schema already covers all three parameters with clear descriptions (100% coverage). The description adds only slight value by restating the default publication behavior for the unpublished parameter, but it is largely redundant with the schema.

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 core action: 'Cria um novo Google Form vazio' (creates a new empty Google Form) and specifies the returned resources (ID, edit link, response link). This distinguishes it from sibling tools that add or modify content within a form, such as add_question or update_form_info.

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 gives implicit usage context by explaining the unpublished parameter and the default published state, but it does not explicitly compare with alternatives like build_form or say when NOT to use this tool. It lacks direct references to sibling tools or exclusions.

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