bulk_move

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

No annotations are provided, so the description carries the full burden. It states that the tool processes the array in a single call, implying efficiency, but does not disclose behavior on error (e.g., invalid slug), return values, or side effects like overwriting. Acceptable for a simple move operation but could be more transparent.

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?

Three sentences, each serves a distinct purpose: action description, efficiency note, and usage guidance with exclusion. No unnecessary words or 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?

The tool is simple (batch move), and the description covers core purpose, usage context, and differentiation from siblings. No output schema is needed. Minor gaps like error handling are not critical for a straightforward operation.

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 100%, so baseline is 3. The description restates schema descriptions ('Lista de slugs (sin extensión .md) a mover' and 'Categoría destino para todas las notas') without adding new semantic detail, so score remains 3.

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 the tool moves multiple notes at once to a single destination category, using verbs like 'mover, reubicar o desplazar'. It distinguishes from sibling move_note by explicitly saying 'No renombra — para renombrar usa move_note una a una', making the batch purpose 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 provides explicit guidance: 'Útil al procesar la bandeja de entrada cuando hay varias notas para la misma carpeta' suggests when to use, and the note about not renaming and the alternative move_note clarifies when not to use it.

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