batch_archive_documents

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

Discloses sequential processing, continues on failure, automatic rate limiting, and the effect on documents (removed from collections but remain searchable). Annotations (destructiveHint: true, idempotentHint: true) are consistent and description adds significant behavioral context beyond them.

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?

Well-structured with short paragraphs, bullet points, and clear sections. Every sentence adds value; no fluff. Front-loaded with purpose and behavior.

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 simple operation (1 param, basic archiving), the description fully covers purpose, behavior, usage, and return type. Output schema exists to detail return values. No gaps.

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?

Only one parameter (document_ids). Schema description coverage is 0%, but description repeats 'List of document IDs to archive' which adds little beyond the schema. No details on format, limits, or constraints for the array items.

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?

Clearly states it archives multiple documents in a batch, distinguishing from siblings like archive_document (single) and batch_delete_documents (deletion vs archive). Specific verb+resource: 'batch archive documents'.

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?

Provides explicit use cases (archive multiple outdated docs, clean collections, batch hide) and a recommended batch size. Lacks explicit when-not-to-use or alternative tools, but context is clear.

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