Import Tracker issue

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds value beyond them by disclosing the admin-only permission requirement and the history-preserving side effect, both of which are meaningful for an import operation. It does not, however, address idempotency or what happens on a duplicate/existing key.

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?

Two short sentences: the first front-loads purpose, scope, and the permission constraint; the second states the return. No filler whatsoever.

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 nested-body import with no output schema, the description covers the essential unknowns: the admin restriction, that history is preserved, and that the imported issue is returned. It leaves minor gaps (duplicate-key behavior, non-idempotency, error modes) that an agent might want before calling.

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% on the single nested body object, and each field (key, queue, summary, createdAt, updatedBy, etc.) is individually documented with constraints and pairing rules. The description adds no parameter-level information, so the 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 ('Import an issue') plus a differentiating qualifier, 'preserving its original history,' which separates it from the plain tracker_issues_create sibling. It stops short of naming that sibling explicitly, so the distinction is inferable rather than stated.

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?

'admin-only back-fill' clearly describes the scenario in which this tool applies rather than routine issue creation, which is meaningful guidance given the ~200 siblings. It never names an alternative tool or an explicit when-not condition, so it falls just short of a 5.

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