Transactional multi-file patch

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

Annotations declare destructiveHint=true, and the description delivers real added value beyond that: strict UTF-8 input, persistent byte backup, forced BOM, atomic replacement, read-back verification, and — critically — that a compile failure restores exact original bytes. That rollback guarantee is exactly the behavioral detail an agent needs before invoking a destructive 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?

One dense semicolon-chained sentence front-loads the core concept, but the fragment 'main.cs requires validate.command to compile its project' reads like extracted example text and muddies rather than clarifies. Tight, but not cleanly structured.

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 multi-file mutation with nested objects and no output schema, the description richly covers behavioral traits but omits several parameters and never says what the 'integrity statistics' or read-back results look like. Enough to understand intent, insufficient to configure the call.

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 coverage is 0% across five parameters including nested replacement and validate objects, so the description carries the full burden and mostly fails. It references validate.command and files implicitly, but says nothing about dryRun, deviceId, deviceName, replaceAll, or oldText/newText semantics, leaving them undocumented everywhere.

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?

Opening phrase 'Transactional source edits' names a specific verb and resource, and the description adds the atomic-replacement/rollback characteristic that separates it from plain writers like fs_write_many or fs_apply_patch_many. It stops short of naming any sibling explicitly, so an agent must infer the boundary itself.

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?

There is no 'use this when / use X instead' guidance anywhere. The only usage-flavored statement, 'Other files support optional validation,' describes behavior rather than a selection condition across the many file-editing siblings (edit_block, fs_apply_patch_many, fs_write_many).

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