Bulk-transition Tracker issues

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

Annotations already establish readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true. The description adds genuinely non-redundant behavior: the operation is asynchronous, returns an operation handle, and must be polled via bulk_get. It stops short of stating failure/partial-application semantics or permission requirements.

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 short sentences with zero waste; the core action and its async nature are front-loaded, and the polling instruction follows immediately.

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 an async bulk mutation with no output schema, the description covers what it does, that it returns an operation, and how to retrieve the result. It could say more about partial-failure behavior or required permissions, but the essential calling contract is present.

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%, so the schema itself documents body, transition, issues, values, and notify. The description adds no meaning beyond that for any parameter, so the baseline 3 applies.

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+resource+scope: 'Start an async bulk status transition over many Tracker issues.' The word 'status transition' distinguishes it from field-level siblings like tracker_issues_update_bulk and tracker_issues_move_bulk, but no sibling is named explicitly, so the differentiation requires inference.

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?

Provides follow-up guidance ('Poll with bulk_get') which tells the agent this is async. However it gives no explicit when-to-use versus alternatives such as tracker_transitions_execute (single issue) or the other bulk siblings, and no exclusions. Usage is implied by 'over many issues' but not stated.

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