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

The 'MUTATING' prefix broadly aligns with the destructiveHint=true annotation, and the description usefully notes that the comment becomes the ticket's first message. It does not disclose side effects an agent would care about for a create tool, e.g. that the requester may be emailed, that a ticket id is returned, or any permission requirements. No contradiction with annotations.

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?

Three very short sentences with the mutation warning and required fields front-loaded, followed by the endpoint. No filler and nothing buried.

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 no output schema, the description omits what comes back from a create call (e.g. the new ticket id, useful for chaining to update_ticket). For a 10-parameter mutation tool this leaves side effects and return semantics to guesswork, though the parameter surface itself is well covered by the 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 100%, so the schema already documents all 10 parameters including the two required ones. The description's restatement that subject and comment_body are required and that the comment is the first message largely duplicates the schema's own wording, adding only marginal semantic value.

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 new support ticket') and the REST endpoint (POST /tickets.json), making the action unambiguous against siblings like zendesk_update_ticket or zendesk_add_ticket_comment. However, it never names or contrasts with those siblings, so it stops short of full differentiation.

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 when-to-use / when-not-to-use guidance and no routing to alternatives (e.g. add_ticket_comment for an existing ticket). The only context is the 'MUTATING' prefix, which signals a write but does not tell the agent when this tool is the right choice.

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