create_ticket

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

With no annotations, the description must carry the full burden of behavioral disclosure. It does reveal that the description field accepts plain-text or HTML and that requester_email defaults when omitted, but it does not mention permissions, idempotency, side effects, or what the response contains.

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 extremely concise: one purpose sentence plus a bullet list of four parameters. It is front-loaded with the primary action and each parameter gets a brief, informative line, with no wasted 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?

For a simple create operation, the description covers the main action and all parameters, and an output schema exists to define return values. However, it omits explicit usage guidance and any preconditions, making it adequate but not fully comprehensive.

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 has no descriptions (0% coverage), so the description fully compensates by explaining each parameter: subject, description, priority (with examples), and requester_email (with default behavior). This adds substantial meaning beyond the bare property names.

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 states 'Create a new Help Desk ticket in ServiceDesk Plus,' which is a specific verb (create) and resource (Help Desk ticket) with a clear system context. This clearly distinguishes it from sibling tools like list_tickets and update_ticket.

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 explicitly mention when to use this tool or any alternatives, so the usage is implied by the name and purpose. It offers no exclusions or comparison to sibling tools like update_ticket or add_ticket_note, leaving the agent to infer the correct context.

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