get_issue_link

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

Annotations already provide readOnlyHint=true, and the description reinforces that it does not mutate data while adding concrete behavioral details: missing resources, invalid identifiers, insufficient permission, and rate limits are surfaced as errors. This provides context beyond the annotation without contradicting it.

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?

The core action and usage guidance are front-loaded and efficient, but the final sentence contains boilerplate about group_id and pagination that does not apply to this tool's schema. The description would be tighter and more accurate without that extraneous clause.

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 simple read-only tool with three fully documented parameters and no output schema, the description covers the action, usage context, and error behavior. It does not explain the concept of an issue link or the return shape, but the low complexity and annotation coverage make the definition sufficiently complete.

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 a baseline of 3 is expected, but the description introduces group_id and 'pagination fields' that do not appear in the schema. It largely restates the schema's project_id guidance rather than adding meaningful semantics, and the irrelevant references actively confuse parameter understanding.

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 clearly states the action ('Get'), the resource ('a specific issue link'), and scope ('specific'), and distinguishes itself from list or search tools by noting when those should be used instead. This effectively differentiates it from the sibling list_issue_links.

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 description gives explicit usage context: use for a known resource or result, and use the corresponding list or search tool when discovering multiple resources. This is direct when-to-use versus alternative guidance.

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