bulk_update_execute

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description adds critical behavioral context: it brands the operation as 'DESTRUCTIVE', mandates a preview step, and discloses that the batch is tagged for rollback. This gives the agent concrete risk-awareness and recovery expectations not present in the schema.

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 compact and front-loaded with the most safety-critical warning. It then lists parameters in a clean Args block with no filler. Every sentence earns its place: the warning, the rollback note, and the parameter definitions.

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 destructive bulk operation, the description includes the essential safety workflow (preview first), rollback indication, and full parameter documentation. An output schema exists, so return-value details are not required. The tool's complexity is well covered by the combination of annotations and description.

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%, so the description carries full weight for parameters. It explains query as a YouTrack search query, command as a YouTrack command, max_results with both default and an explicit upper bound (100) absent from the schema, and instance as optional. This meaningfully enriches the bare schema titles.

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?

Description states a specific verb ('Execute') and resource ('bulk update'), and immediately distinguishes itself from the preview sibling by warning 'call bulk_update_preview first'. It clearly identifies the operation as the execution phase of a bulk update, which an agent can readily differentiate from other update tools.

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 explicitly instructs to call bulk_update_preview first, which is a clear precondition and safety guideline. It also implies execution should follow preview, though it does not explicitly list alternatives or exclusions beyond this. The directive is actionable and precedes parameter details.

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