listJiraIssueChangelogs

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds real behavioral value beyond them by stating the result is 'paginated oldest-first', which tells the agent about ordering and pagination. It does not explain result volume, page sizes, or how to page further.

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 front-loaded sentence with no filler or repetition. It is appropriately terse, though at the cost of the detail needed elsewhere; the awkward 'An work item's' phrasing is a minor blemish.

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 paginated read with read-only annotations and no output schema, the description covers ordering and pagination, which are the key behaviors. It is nonetheless thin given 0% schema coverage and no explanation of the parameters or what a changelog entry contains.

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 0%, so the schema contributes nothing and the description must compensate — but it only hints at pagination via 'paginated', never explaining startAt or maxResults, and never clarifying that issueIdOrKey is the required issue identifier. This leaves all three parameters effectively undocumented.

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 precisely — a work item's field-change history — so an agent can tell this returns changelog entries rather than comments or worklogs. It lacks any explicit verb ('list') and offers no differentiation from sibling read tools like getJiraIssue, but the scope is clear from the noun phrase and pagination note.

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?

There is no when-to-use guidance, no mention of prerequisites like needing the issue key in hand, and no routing to or away from siblings such as listJiraIssueWorklogs or listJiraIssueComments. The agent must infer usage entirely from the name.

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