conduyt_create_form

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

No annotations are provided, so the description carries the full behavioral burden. The only behavior disclosed is automatic slug generation, which is already stated in the schema's slug property description, leaving permission requirements, side effects, and what happens to omitted optional settings entirely unaddressed.

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, zero filler, with the core action front-loaded and the slug fallback following. The size is appropriate for a simple creation tool.

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 an 8-parameter mutation with no annotations and no output schema, the description omits what a successful call returns (id/slug of the created form) and how the fields/settings objects should be shaped. Adequate to call, but not complete for an agent working without annotations.

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 100%, so every parameter including name, slug, fields, isActive, settings, redirectUrl, and thankYouMessage is already documented in the schema. The description adds nothing beyond the schema and merely restates the slug default rule, which fits the baseline 3.

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?

Clear verb+resource: 'Create a new web form' states exactly what is produced, and it is distinguishable from conduyt_list_forms / conduyt_get_form. It does not, however, differentiate itself from other creation siblings (booking pages, templates, call flows) beyond the resource noun.

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 use this versus conduyt_list_forms, conduyt_get_form, or conduyt_create_booking_page, and no prerequisites or exclusions are stated. Usage is only implied by the verb 'Create'.

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