Get Tracker issue checklist

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description earns credit by adding return behavior the annotations cannot: a flat array, and an empty list when the issue has no checklist. It stops short of permissions, pagination or error behavior, so not a 5.

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?

Two compact sentences, zero filler, return shape front-loaded and the id-chaining note kept to a short trailing clause. Nothing could be cut without losing information.

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 one-parameter read tool with rich annotations and no output schema, the description covers what the agent actually needs: what is returned, the field set, and the empty case. Only secondary details (permissions, error handling) are absent, which is a minor gap.

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 parameter (issue_key) with 100% schema description coverage including an example format (QUEUE-123), so the schema carries the burden. The description adds nothing about the parameter, which is fine but leaves this at the baseline.

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 a specific resource (checklist items on a Tracker issue) and even enumerates the item fields returned (text, done flag, assignee, per-item deadline). By pointing to checklists_update / checklists_delete as consumers of the returned ids, it also distinguishes itself from the mutating siblings.

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 is only implied: the reader infers this is the read step that precedes update/delete, since the description says its item ids feed those tools. There is no explicit when-to-use statement, no exclusion, and no mention of related siblings such as tracker_entities_checklists_* or tracker_checklists_create/clear.

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