Create Tracker issue type

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

Goes well beyond the annotations by disclosing that issue types are organisation-wide, that there is no delete endpoint, and that creation leaves permanent residue — critical irreversibility context. This is compatible with destructiveHint=false (nothing existing is destroyed) and materially improves on the structured hints.

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, front-loaded segments: purpose, then the caution, then a compact parameter gloss. No filler and the most consequential warning is prominently placed.

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 single-parameter create tool with annotations covering the safety profile and no output schema, the description supplies purpose, irreversibility, and parameter meaning. Nothing an agent needs to call it correctly is missing.

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 already 100%, and the description still adds value by explaining that 'key' is the latin identifier and 'name' carries the ru/en display names, clarifying the role of the nested localized object. Baseline 3 is exceeded, though no additional format constraints are given.

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+resource ('Create an org-global issue type') and clarifies with an example ('a new kind of task'). The 'org-global' scope and the issue-type framing cleanly separate it from sibling issue-level creators like tracker_issues_create.

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 org-wide scope and permanence caution implicitly tell the agent this is a heavyweight, rarely-invoked operation, but there is no explicit when-to-use guidance or named alternative (e.g. tracker_issuetypes_update for modification). Usage is inferred rather than stated.

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