Create Zendesk Ticket

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

The description 'create a new ticket' aligns with annotations (readOnlyHint=false, destructiveHint=false), but adds no additional behavioral context such as side effects, authentication requirements, or rate limits. Since annotations already indicate a non-destructive write, the description offers no extra value.

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, compact sentence that conveys the core purpose and key optional parameters. No unnecessary words.

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?

With 8 parameters, no output schema, and minimal annotations, the description fails to explain return values, error behavior, or outcomes. For a create operation, more detail (e.g., what is returned) is expected.

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 low (25%); the description lists some optional fields (priority, type, assignee, tags) but omits others like group_id and custom_fields. This partially compensates for the schema's lack of descriptions but does not fully explain all 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 specifies the action 'create' and the resource 'Zendesk support ticket', listing required fields and optional parameters. Although it doesn't explicitly distinguish from siblings, the verb 'create' naturally sets it apart from update or read tools.

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 guidance on when to use this tool vs alternatives, nor does it mention prerequisites, restrictions, or when not to use it. It simply states what the tool does.

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