Create Tracker field category

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. The description adds genuinely non-derivable behavior: the category is org-global (affects the whole organization, not one queue/project) and cannot be undone via the API, which materially changes how careful an agent should be.

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 tight sentences: purpose first, then required fields, then the caution — appropriately front-loaded with no filler. It could be marginally tighter by folding the required-params sentence into the schema-reliant flow, but nothing is wasted.

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 100% schema coverage and no output schema, the description supplies purpose, required inputs, and the irreversible org-global consequence. Missing details such as auth/permission requirements or what the call returns are minor given the structured data already present.

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 the nested name (en/ru), order, and description fields are already documented in the schema. The description restates name and order requirements but adds no format or semantic detail beyond what the schema says, and it omits the optional description param entirely. Baseline 3 applies.

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 gives a specific verb and resource ('Create a field category') and adds a functional gloss ('a grouping bucket for issue fields in the UI') that separates it from generic field tools like tracker_fields_create. It does not explicitly contrast itself with the sibling tracker_fields_categories_update, but the create/update distinction is unambiguous from the name plus 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?

There is no when-to-use guidance, no prerequisites, and no mention of an alternative (e.g. update vs create, or how categories relate to fields). The 'Required: name and order' line is a restatement of the schema, not usage guidance. Only the CAUTION hints that this is an operation to invoke deliberately.

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