Add Issue Checklist Items

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

Beyond the readOnlyHint=false annotation, the description discloses important behavioral details: the checklist is created if it does not exist, items are appended in the given order, and the response contains the checklist after addition. This gives the agent a clear model of the operation's side effects and return semantics.

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 concise, front-loaded with the core action, and every sentence adds meaningful information: action, creation behavior, ordering, and return value. There is no redundant or filler content.

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 two required parameters, a full input schema, an output schema, and readOnlyHint=false, the description is complete enough. It explains the mutation behavior, the ordering guarantee, the auto-creation behavior, and what the caller should expect in the response, so an agent can invoke it correctly without missing key context.

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 100%, and the schema already documents issue_id format and items as an array with an example. The description adds minor behavioral context ('items are appended in the order given'), but the schema already conveys the same ordering intent in the items description, so the description adds limited value beyond the structured schema.

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 uses a specific verb ('add') with a clear resource ('items to the checklist of a Yandex Tracker issue') and clarifies that multiple items can be added. It also specifies the 'one or more items' semantics and the append behavior, making it easy to distinguish from sibling tools like issue_update_checklist_item or issue_delete_checklist_item.

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 implies usage through its verb and behavior but does not explicitly state when to prefer this tool over alternatives such as issue_update_checklist_item or issue_delete_checklist_item. It does clarify that the checklist is created on demand, which helps an agent understand the tool's effect, but no explicit when-to-use or when-not-to-use guidance is provided.

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