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

Annotations already cover the safety profile (readOnly=false, idempotent=true, destructive=false, openWorld=false), but the description adds real value on top: the required scope, the concrete idempotency mechanism (new UUID per intended creation, reuse with identical args on retry), and the side effect that assignment can notify a user or kick off an agent.

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?

Five tight sentences, front-loaded with the action, then routing, auth, idempotency, side effects and the limitation. Every sentence carries distinct information and none restates the schema or annotations.

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 mutation tool with no output schema, the description covers auth, idempotency, side effects and limitations well. It stops short of saying what a successful call returns (e.g. the new ticket ID), which matters for chaining into get_ticket or add_ticket_comment, and it leaves most of the 11 params uncharacterized.

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 0% across 11 params, so the description carries the burden. It does well on the most consequential param, requestId (fresh UUID per creation, reuse only for identical retries), and points at where board/column/assignee/repository IDs come from, but it adds no meaning for title, description, projectId, priority, dueAt or startsAt, leaving most fields undocumented.

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 clear verb+resource ("Create a ticket") and scopes it as parity with the dashboard, which an agent can map to the create path among the get_ticket/update_ticket/delete siblings. The phrasing "same fields and behavior as the dashboard" is a soft, out-of-band reference rather than an explicit differentiator from the sibling CRUD 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?

Explicitly routes lookups to get_ticket_options for boards, columns, assignees and repositories, states the tickets:write permission prerequisite, and gives the retry contract for requestId. It also flags the assignment branch (notify vs. start agent) and an exclusion (file uploads not supported).

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