create_ticket

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It thoroughly explains Markdown parsing in the description field, the behavior of landing in the first column when neither status nor status_uuid is given, position-based ordering, and the idempotency caveat that calling twice creates two tickets. It also reveals the response structure (uuid and version), making the agent aware of post-call implications.

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 dense but every sentence provides critical operational detail: parameter selection, Markdown behavior, positioning, response contents, and retry strategy. It is front-loaded with the core action and flows logically without redundant phrases, making it efficient for agent consumption.

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 create operation with 8 parameters and no output schema, the description fully compensates by explaining the return value (new ticket with uuid and version), the default column behavior, and the idempotency caveat. It also covers failure handling via list_tickets. This is a complete context for an agent to invoke the tool correctly and follow up appropriately.

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 coverage is 100% (all 8 parameters have descriptions), so the baseline is 3. However, the description adds valuable semantic depth beyond the schema: it clarifies the mutual exclusivity of status and status_uuid, explains that position is a sort key not an index, and notes that returned positions are decimal strings sent as numbers. This goes above the baseline by providing practical contextual semantics.

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 opens with 'Create a ticket on a board', which is a specific verb+resource statement that clearly defines the tool's purpose. It also distinguishes the tool from siblings like update_ticket, archive_ticket, and delete_ticket by stating it creates new tickets, not modifying or deleting existing ones.

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 provides explicit usage guidance such as choosing between status/status_uuid and handling timeouts by using list_tickets with the title as a fallback. This gives the agent clear direction on when to use this tool and how to recover from ambiguous failures, which is a strong alternative-oriented explanation.

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