listJiraIssueComments

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The one piece of added context is 'Paginated', which usefully flags paging behavior, but the description says nothing about ordering defaults, result shape, or rate limits.

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?

A single compact sentence with no filler and the key pagination framing front-loaded. It is efficient, though so terse that it borders on under-specification for a 5-parameter tool.

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 tool with 5 parameters at 20% schema coverage and no output schema, the description is far too thin. It neither explains paging controls nor parameter usage, leaving real gaps an agent must guess around.

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 20% across 5 parameters (only orderBy is annotated). The description adds no meaning for startAt, maxResults, expand, or issueIdOrKey beyond the word 'Paginated', so it fails to compensate for the low coverage.

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 names the resource (comments) and scope (for a Jira work item) and adds 'Paginated', but it is essentially a noun-phrase restatement of the tool name with no explicit verb and no differentiation from siblings like addOrEditJiraIssueComment. An agent can infer it is a read/list operation, but the phrasing is thin.

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?

No when-to-use guidance and no reference to alternatives. It never clarifies the relationship to addOrEditJiraIssueComment (the mutating counterpart) or to other list tools such as listJiraIssueWorklogs or listJiraIssueChangelogs. The agent must infer usage entirely.

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