zda_create_ticket_form

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

With no annotations, the description must disclose behavioral traits. It indicates a write operation (creation) but lacks details on authentication, rate limits, error handling, or side effects like whether existing forms are overwritten, leaving significant gaps.

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 a single sentence followed by a list of common fields, with no wasted words. It is 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?

While the description covers purpose and parameter structure, it omits return values, error behavior, and does not fully explain the nested object complexity (e.g., conditions, actions). This leaves gaps for a create operation, though the input schema description partially compensates.

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 description adds crucial meaning beyond the raw schema: it explains the 'data' parameter is passthrough, lists example fields, and warns against wrapping in an envelope. The tool description also lists common fields, fully compensating for the single parameter.

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 'Create a new Zendesk ticket_form' with a specific verb and resource, and lists common fields, distinguishing it from sibling create tools for other objects like automations or views.

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 does not provide explicit guidance on when to use this tool versus alternatives (e.g., update or other create tools), nor does it mention prerequisites or exclusion scenarios, offering only the basic context of creation.

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