jira_issues_create

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

Annotations (readOnlyHint=false) are minimal; description adds that custom fields must use field IDs and returns {key, id}. Does not disclose potential side effects beyond creation (e.g., notifications). Adequate but not rich.

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 sentences, each essential: action, pre-requisite, custom field note, return value. No redundancy, front-loaded purpose.

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?

Given 8 parameters with 3 required and no nested objects, description covers purpose, parameter nuance, and return shape. Pre-requisite for createmeta is mentioned. Missing output schema details but return is described in text.

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%, baseline 3. Description adds value by clarifying custom fields must use field IDs ('customfield_XXXXX') and stating return returns {key, id}, which is not in schema. Exceeds baseline.

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 clearly states 'Create a new Jira issue.' It specifies verb (create) and resource (Jira issue), and distinguishes from siblings like jira_issues_bulk_create and jira_issues_update by focusing on single issue creation with pre-validation guidance.

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 advises to use jira_issues_get_createmeta first to check required fields for the project/issue type. This provides clear when-to-use guidance. Lacks explicit when-not-to-use but context is clear.

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