redmine_repository_revision_link_issue

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the permission requirement, but does not disclose whether linking is idempotent, whether it can be repeated, what side effects occur on the issue or changeset, or what the response looks like. For a mutating POST operation, this is a meaningful transparency gap.

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 description is two sentences with no wasted words. The first sentence front-loads the purpose, and the second adds the endpoint and a key prerequisite, so 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 simple link operation, the essential invocation details are present: all four required parameters are implied by the endpoint and action, and the permission note is useful. However, with no output schema and no annotations, the description does not explain success/error behavior or the response format, so an agent cannot fully anticipate the result of the call.

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 only 25%, so the description must compensate for the undocumented parameters. The endpoint template maps `:id`, `:repository_id`, and `:rev` to parameters, and the action explains `issue_id` generally, but it does not clarify the format of `rev` (e.g., hash vs number), whether `repository_id` accepts an identifier, or the meaning of `issue_id` beyond the obvious. This is only marginal value over the schema.

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 states a specific verb ('Link') and resource ('an issue to a repository changeset'), which clearly conveys the action. It also includes the exact HTTP endpoint, and the sibling `redmine_repository_revision_unlink_issue` provides an obvious inverse contrast, so an agent can distinguish this from other repository tools without inspecting schemas.

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 clear context for when to use the tool: associating an issue with a changeset, and it mentions the prerequisite API permission on the repository. It does not explicitly say 'use unlink_issue to reverse this' or list exclusions, but the inverse sibling name and the linking verb make the intended usage sufficiently clear.

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