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

No annotations are provided, so the description carries the full behavioral burden. It does well on data-scoping traits that aren't obvious: links are filtered to 'only ones you can read', relation direction is explained from this issue's side, and null cases for latestAgentRun and source are spelled out. However, it never states error behavior for an unknown or unreadable key, nor confirms the operation is a pure read with no side effects, which is the main gap for a zero-annotation tool.

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?

Purpose is correctly front-loaded in the first clause, and every later clause maps to a real returned field, so little is wasted. The problem is structure: it is one enormous run-on sentence with em-dash-nested asides that is hard to scan, where a short field list would have been far more readable.

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?

With no output schema and no annotations, the description correctly takes on the burden of explaining the return payload, and it covers the non-obvious fields (statusId/epicId resolution, statusCategory meanings, canEdit/canDelete, links with directional relations and an ambiguity-dissolving example, latestAgentRun state, Telegram source with a concrete URL shape). Only failure modes and side-effect guarantees are missing.

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?

There is a single required parameter and the schema already documents it at 100% coverage with an example. The description reinforces this by tying the key to the tool's contract ('by its key') and formats the example identically, but adds no new semantics such as case sensitivity or accepted key formats.

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 opening clause states a specific verb, resource, scope and selector: fetch a single issue's title, full content and attachments by its key, with a worked example ('BRD-42'). The singular 'one issue' plus the keyed lookup cleanly separates it from list_issues and the other list-oriented siblings mentioned later.

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?

Usage context is clear: call this when you have an issue key and need the single issue with its relations and metadata. It also routes the agent onward to the right sibling for sub-resources (list_issue_comments for comments, get_attachment for files, list_statuses to resolve statusId/epicId). There is no explicit exclusion such as 'use list_issues to find a key you don't have', so it stops short of a full when/when-not statement.

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