Import Tracker issue link

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

Annotations cover the safety profile (not read-only, not destructive, not idempotent, open world), and the description adds two genuinely behavioral facts beyond them: the operation is admin-only and the return value is the imported link. It would be a 5 with more on what happens on duplicate links or invalid metadata.

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, zero filler, with the purpose clause front-loaded and the return behavior stated second. Every sentence earns its place.

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 2-parameter import tool with a fully described schema and no output schema, the description covers the admin restriction, the metadata-preservation intent, and the return shape. Only edge-case behavior (duplicates, validation failures) is unstated.

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% and the nested body object is thoroughly documented (relationship, issue, createdAt, createdBy, updatedAt/By pairing), so the schema carries the load. The description adds no parameter-level detail beyond that, matching the baseline of 3.

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?

Specific verb (Import) plus resource (issue link) plus a distinguishing purpose clause: preserving original creation metadata. That implicitly separates it from tracker_links_create/tracker_entities_links_create, though no sibling is named so it lands just below 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?

The parenthetical "(admin-only)" states a precondition, and "preserving its original creation metadata" hints at the migration/backfill use case, but there is no explicit when-to-use guidance and no named alternative such as tracker_links_create for ordinary linking.

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