get_checklist

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

readOnlyHint=true already tells the agent this is a safe read. The description adds one genuinely useful behavioral detail, that returned items carry their identifiers (which is what the update/delete siblings need), but says nothing about permissions or ordering/limits on the returned items.

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; the resource comes first and the clarifying detail about identifiers is appended efficiently.

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?

An output schema exists, so return values need not be described, and this is a simple one-parameter read. Still, the description offers no routing guidance against get_checklist_report and no clarification of the issue_id format, so it is only minimally complete.

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% and the single parameter issue_id carries no schema documentation. The description implies the argument is an issue ('чек-листа задачи') but never clarifies whether it expects a numeric ID or a key such as 'PROJ-123', leaving a real ambiguity unaddressed.

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?

States a specific verb and resource: retrieving the checklist items of an issue, plus the detail that their identifiers are included. It does not explicitly differentiate itself from the sibling get_checklist_report, so an agent must infer which one to reach for from the name alone.

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 statement of when to use this tool versus get_checklist_report or the add/update/delete_checklist_item siblings. The only implied context is that it is a read operation on an existing issue's checklist.

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