Get a single issue comment

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the agent knows this is a safe, read-only operation. The description adds the endpoint path and authorization class, which provides some context but does not disclose additional behavioral traits beyond what annotations already cover. No contradiction with annotations.

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 brief, consisting of three short sentences. The first sentence repeats the title, which is slightly redundant, but overall there is no wasted content. The structure is clear and front-loaded with the core purpose. It earns a high score for conciseness, though the redundancy prevents a perfect 5.

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?

Although the tool has an output schema (so return values need not be explained) and annotations cover safety, the description lacks critical context: it does not describe what an 'issue comment' is, how to obtain the required IDs, or any special behavior (e.g., auth requirements beyond the annotation). The missing parameter semantics further detract from completeness.

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 schema description coverage is 0%, meaning no parameter descriptions in the input schema. The description fails to compensate by explaining what the 'id' and 'commentId' path parameters represent. It merely includes them as placeholders in the URL template. This omission leaves the agent without necessary semantic context for the parameters.

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 'Get a single issue comment', which is a specific verb ('Get') and resource ('single issue comment'). The tool name and title reinforce this, and it distinguishes itself from siblings like pc_get_issues_by_id_comments (list) and pc_delete_issues_by_id_comments_by_comment_id (delete) by focusing on a single entity.

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 does not explicitly provide guidance on when to use this tool versus alternatives. While the name and title imply it is for retrieving a specific comment, there is no mention of when to prefer this over listing comments or other related operations. The inclusion of the endpoint and authorization class is informative but does not address usage selection.

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