bulk_update_execute

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

With no annotations, the description carries the full burden. It declares the tool as 'DESTRUCTIVE', mentions rollback tagging, and documents the max_results cap (default 50, max 100). This provides essential behavioral insight beyond 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 concise (5 lines) with a clear warning upfront. It front-loads the critical purpose and safety instruction, then lists parameters efficiently. Every sentence adds value.

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 tool complexity (4 params, mutation, output schema exists), the description covers key aspects: purpose, safety warning, parameter meanings, and rollback capability. It doesn't detail the return value, but the output schema exists, so this is acceptable.

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 must compensate. The docstring explains 'query', 'command', 'max_results', and 'instance' with context (e.g., 'YouTrack search query', 'default: 50, max: 100'), adding meaning the schema lacks.

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 'Execute a bulk update' and distinguishes it from the sibling 'bulk_update_preview' by explicitly referencing it. The purpose is specific and unambiguous.

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 recommends calling 'bulk_update_preview first' and warns about the destructive nature, guiding proper use. While it doesn't exhaustively list when not to use, the guidance is sufficient for the agent.

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