Create Form

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write and external-visibility profile is covered structurally. The description adds real value by explaining that the idempotency key exists for safe retries. It omits the hard limits the schema imposes (max 10 fields, enumerated field_ids) and says nothing about permissions or what happens on key reuse.

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?

Two short sentences with the core action front-loaded and no filler. Efficiency is fine; the problem is under-specification rather than verbosity.

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?

A four-required-parameter mutation tool with 0% schema coverage, a nested field array with enumerated ids, and no output schema needs far more than two sentences. The description leaves the agent to infer field composition and payload shape entirely from the raw schema.

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 0%, so the description carries the full burden and only partially delivers: it hints that idempotency_key is a 'stable retry key' and that text must be localized. The four required parameters are otherwise unmentioned — nothing explains what 'name' vs 'guide_text' mean, or how the 'fields' array should be composed.

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 and resource: 'Create a workspace form.' The scope is narrow enough that an agent can distinguish it from update_form, get_form and delete_form in the sibling list without opening any schema.

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 statement of when to use this versus update_form or create_campaign-style setup flows, and no prerequisites or permission requirements. 'Use explicit localized text for the creator audience' is content guidance, not selection guidance.

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