Import Tracker issue comment

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

Annotations already declare the mutation/safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the bar is lower. The description adds real value beyond them: the admin-only authorization requirement and the fact that author/timestamp are preserved from the payload rather than set to now. It omits conflict/duplicate behavior, which matters given idempotentHint=false.

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 sentences, zero filler, with the key authorization and preservation behavior front-loaded before the return note.

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?

Covers authorization, import semantics, and the return value despite there being no output schema, and the 100%-documented schema carries parameter detail. Minor gaps remain around duplicate/conflict handling for a non-idempotent write.

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 schema fully documents issue_key and the nested body (text, createdAt, createdBy, optional updatedAt/updatedBy). The description only echoes the authored/timestamped nature of the payload and adds no syntax or format detail. 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?

States a specific verb+resource (import a comment onto an issue) and the discriminating behavior ('preserving its original author and timestamp') separates it from the create sibling. It does not name an alternative explicitly, so it stays just short of 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?

The '(admin-only)' qualifier gives a clear precondition for use, but there is no guidance on when to prefer this over tracker_comments_create or tracker_issues_import. Usage context is implied by the 'import' semantics rather than stated.

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