jira_create_issue

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

No annotations provided, so the description must disclose behavioral traits. It only states 'create', implying mutation, but fails to mention side effects, permissions, required parameters (projectKey, summary), or output. Minimal behavioral insight.

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 a single concise sentence. It is front-loaded and not verbose, but could include more critical details without sacrificing brevity. Adequate but not ideal.

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?

Tool has 9 parameters, no output schema, and no annotations. The description provides no completeness: no explanation of return value, required fields, usage patterns, or error behavior. Lacks essential context for proper invocation.

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?

Input schema has 100% description coverage, so the schema already documents parameters. The tool description adds no parameter meaning beyond what schema provides. Baseline score of 3 is appropriate as description does not reduce ambiguity.

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 'Creates a new JIRA issue' using a specific verb and resource. It distinguishes from sibling tools like jira_update_issue or jira_get_issue by focusing on creation, but lacks additional detail such as required fields or scope.

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?

No guidance on when to use this tool instead of alternatives like jira_add_comment or jira_update_issue. No mention of prerequisites, required fields, or prohibitions. The description provides no context for when creation is appropriate.

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