create_form

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

Discloses side effects (creates empty form owned by user) and required OAuth scope. With no annotations, the description carries the transparency burden and does it well, though it could mention failure modes or response structure.

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?

Three concise sentences: purpose, side effects/alternatives, and scope. No unnecessary words, well front-loaded.

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 the tool is a creation action with an output schema, the description covers creation, side effects, follow-up steps, and authorization. Minor omission: does not explain that the created form is empty and requires additional calls, but that is implied by the batch_update_form reference.

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%, so baseline is 3. The description only reiterates 'title and optional description' which is already in the schema. It does not add extra context for the user_google_email or document_title parameters.

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 it creates a new Google Form with a title and optional description. It distinguishes itself from siblings like batch_update_form (modifies) and get_form (reads) by focusing on creation.

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?

Explicitly tells when to use this tool (to create a new form) and provides alternatives for adding items (batch_update_form) and inspecting (get_form). Also mentions required OAuth scope.

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