Edit Tracker issue type

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the partial-update semantics and the purpose of version (guarding against concurrent edits), but the schema's body description already states that omitted fields stay unchanged, and nothing is said about what happens on a version conflict or what permissions the edit requires.

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?

Front-loaded with the action and scope, followed by two short, purposeful notes on id format and version locking. Only the partial-update clause is mildly redundant with the schema's body description.

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 3-parameter mutation tool with a nested body object, no output schema, and full schema coverage, the description covers the essentials: partial-update behavior, the id-vs-key distinction, and the concurrency guard. It could still say more about authorization requirements and conflict behavior, but nothing needed to invoke the tool 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 100%, so the baseline is 3, but the description genuinely adds meaning: it clarifies that issue_type_id is the numeric id rather than the key and explains why version should be passed. Note the tension with the schema text, which says "Issue type id or key" — the description is stricter, which is useful but inconsistent with the field documentation.

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 and resource ("Edit an org-global issue type") and pins the scope to org-global types, which separates it from the tracker_issuetypes_create/list siblings by verb. It never names a sibling tool or contrasts with the other *_update tools (fields, statuses, resolutions), so it stops short of a 5.

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?

Usage is only implied: PATCH-style partial edits and the optimistic-locking note about version give an agent some sense of when this tool fits. There is no explicit when-to-use or when-not-to-use guidance, and no routing against alternatives such as tracker_issuetypes_create or the bulk update tools.

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