create_issue_type

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

Beyond annotations, the description adds 'Guarded: requires confirm:true' and 'Issue types are global across the instance.' It also implies high-impact action via the schema, which annotations (destructiveHint: false) do not fully capture. The 'admin only' requirement is extra context.

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 extremely concise at two sentences, with no fluff. It front-loads the core purpose and critical constraints, making it easily scannable.

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?

While the description covers guard, admin requirement, and global scope, it does not describe the return value or error cases. For a creation tool with no output schema, mentioning what the tool returns (e.g., the created issue type details) would improve completeness. Current description is adequate but not fully complete.

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 100%, so baseline is 3. The description adds context about the guard (confirm parameter) but does not substantially improve understanding beyond what the parameter descriptions already provide. It mentions 'admin only' which is not in schema, adding some value.

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 the verb 'creates', resource 'new issue type', and scope 'global across the instance'. It effectively distinguishes from sibling tools like create_story and create_project, as no other sibling creates issue types.

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 explicitly mentions 'admin only' and 'requires confirm:true', providing clear context on when to use. However, it does not explicitly state when not to use or suggest alternatives, but given the unique resource, the guidance is adequate.

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