Create ticket from structured context

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=true, so the write/safety profile is covered. The description adds that it 'builds a consistently formatted description', which explains a real behavioral trait beyond the annotations, but says nothing about required permissions, what the resulting description looks like, or what identifying data comes back.

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 short sentences: action first, then the formatting behavior, then the duplicate-check pointer. No filler and no restatement of the tool name.

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 21 parameters, no output schema and only 62% schema coverage, the description should carry more weight than it does. It omits what the tool returns (e.g. the created issue key), how the sections are ordered or rendered, and how the many optional attributes interact with the generated description.

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 62%, so roughly a third of the 21 parameters are undocumented anywhere. The description's field list (problem, context, reproduction steps, expected/actual, acceptance criteria, technical notes, links) does convey that these inputs are composed into a formatted description rather than passed raw, which is value beyond the schema, but it ignores site, assignee, priority, parentKey, labels, dueDate, storyPoints and customFields entirely.

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 ('Creates a well-structured ticket') and enumerates the structured content it accepts, which is more than the title restates. However, it never distinguishes itself from the closely-named sibling jira_create_issue, so an agent cannot tell from the description alone which creator to choose.

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?

It points at one sibling, jira_find_duplicate_ticket, but only with the hedged 'when appropriate', giving no concrete condition. There is no guidance at all versus jira_create_issue, jira_create_epic, jira_create_child_issue or jira_create_subtask, all of which are viable alternatives in this family.

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