batch_array_remove

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

With no annotations, the description carries full burden. It lists return values (updated_count, updated_files, warnings) and clearly states three skip conditions, plus notes that files are only counted if modified. This fully discloses behavior.

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 with a clear structure: main sentence, Args/Returns/Notes sections. Every sentence provides value, no fluff.

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 presence of an output schema (seen in context), the description does not need to detail return format further. It covers all necessary aspects: purpose, parameters, and behavioral notes, making it complete for a batch operation tool.

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% (no descriptions in schema), so description must compensate. It defines glob with example, property as 'Name of the array property', and value as 'Value to remove', adding significant meaning beyond the bare schema names.

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 explicitly states 'Remove a value from an array property in multiple files...' which is a specific verb+resource combo. It clearly distinguishes from siblings like batch_array_add (adds value) and batch_array_replace (replaces value).

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 'Notes' section provides detailed edge-case behavior (skipping if property missing, value missing, or property not an array), guiding the agent on when the tool has no effect. However, it does not explicitly compare with siblings or provide when-to-use vs alternatives.

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