bulk_update_preview

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description's 'dry run' reinforces this. It adds valuable behavioral details about the max_result cap (default 50, max 100) that could affect the number of issues shown, beyond what the schema defines.

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 well-structured: the purpose statement is front-loaded, followed by a clean parameter list. Every sentence contributes meaning without redundancy.

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?

Given the output schema exists and annotations cover the safety profile, the description provides all necessary context: purpose, sequencing relative to bulk_update_execute, parameter meanings, and the max_results limit. Nothing essential for an agent to invoke it correctly is missing.

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%, but the description fully compensates by explaining each parameter: 'query: YouTrack search query', 'command: YouTrack command to apply', 'max_results: Max issues to preview (default: 50, max: 100)', and 'instance: YouTrack instance (optional)'. This adds meaning beyond the bare 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?

The description clearly states 'Preview which issues would be affected by a bulk update (dry run)', which is a specific verb, resource, and scope. It also distinguishes itself from the sibling tool bulk_update_execute by explicitly positioning itself as the pre-execution preview step.

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 'Call before bulk_update_execute', giving a direct usage sequence. This makes it clear when to use this tool relative to its primary alternative, and the dry-run framing implies it is meant for validation before destructive execution.

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