Delete Tracker issue remote link

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is structured. The description adds the irreversible warning and states the return behavior (acknowledgement on success), which is genuinely additive for a mutating call.

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 tight sentences with the destructive nature front-loaded and the dependency stated second. No filler or restated title.

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?

No output schema exists, but the description compensates by saying an acknowledgement is returned. Combined with the irreversible warning and the required-parameter list, an agent has enough to call it correctly.

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 both parameters are documented there, including the link_id provenance. The description's 'get link_id from remotelinks_list' duplicates the schema text rather than adding syntax or format detail, so 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 (Remove) and resource (remote/external-application link from a Tracker issue) plus the target entity, which cleanly separates it from tracker_remotelinks_list and tracker_remotelinks_create.

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?

Gives the prerequisite flow explicitly (get link_id from remotelinks_list) and warns the action is irreversible. It stops short of naming when-not or distinguishing itself from the other link-delete siblings such as tracker_links_delete or tracker_entities_links_delete.

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