bulk_move

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

With no annotations, the description bears full responsibility for disclosing behavioral traits. It only restates the action without mentioning irreversibility, required permissions, notification behavior, or how optional params like 'notify' and 'move_all_fields' affect the operation. This is a significant gap for a mutation tool.

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 a single, front-loaded sentence with no wasted words. It efficiently states the core action and destination, making it easy for an agent to parse and understand the tool's primary purpose.

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?

The presence of an output schema and full parameter descriptions covers return values and parameter semantics. However, the description omits usage guidance and behavioral context, leaving the agent with insufficient information to distinguish this from similar bulk operations or to anticipate side effects.

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 parameter meanings are fully documented in the schema. The description adds no additional semantic value beyond what the schema already provides, such as examples or cross-parameter relationships.

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 clearly states the action (move), the resource (issues), and the target (another queue). It distinguishes from sibling tools like bulk_transition (status change) and move_issue (single issue move) by specifying 'bulk' and 'queue'.

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 context is implied by the 'bulk' keyword and 'another queue' destination, but no explicit alternatives or when-not-to-use guidance is provided. It does not reference the sibling move_issue for single-issue moves, leaving the agent to infer the scope.

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