get_issue_comment_by_comment_id

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds only the HTTP method and path, which is not behavioral context. It does not disclose what the response contains, potential errors, or any other behavior beyond what the annotations imply.

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 exceptionally concise, containing only the essential information: the action, the endpoint, and the parameter. There is no redundant fluff, and the structure (action, URL, args) is immediately scannable. 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 get-by-ID tool with an output schema present, the description is mostly adequate. It covers the action and the parameter, and the annotations handle safety. However, it lacks any note about return value structure, error conditions, or permissions. Given the simplicity, it is sufficient but not thorough.

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?

The description clarifies that comment_id is a 'Path parameter', which adds a small semantic detail not present in the input schema (which only has a title). However, it does not explain the meaning, format, or purpose of the comment_id beyond being an identifier. Since the schema coverage is 0% and there is only one parameter, this minimal clarification earns a middle score.

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 'Get issue comment' which clearly identifies a read operation on a specific resource. The tool name and the included endpoint (GET /api/v1/issueComment/{commentId}) make it unambiguous that it fetches a single comment by ID, distinguishing it from get_issue_by_issue_id and other related tools. However, it is terse and could explicitly say 'by comment ID' for extra clarity.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that this is the dedicated read operation for a specific comment, nor does it reference any conditions, exclusions, or sibling tools. An agent is left to infer usage from the name alone.

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