bulk_export_archives_text

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

With no annotations, the description carries full burden. It discloses file naming, format details, recursive targetDir creation, per-id status returns, and non-aborting failures. This adds significant behavioral context beyond the input 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?

Four sentences, no fluff. Every sentence contributes: purpose, naming, formats, directory creation, batch behavior, and pairing advice. Highly efficient and front-loaded.

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 no output schema, the description mentions per-id status but omits exact format or overwrite behavior. However, it provides enough context for an agent to use the tool effectively with related archival tools. Minor gaps prevent a 5.

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% and provides basic parameter descriptions. The description adds meaning: 'named by the archive id' for ids, and explains the format enum values ('md — with header', 'txt — plain transcript', 'json — full entry metadata + text'), enhancing the agent's understanding.

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 action ('Export the transcript text'), the resource ('multiple archive entries'), and the destination ('to a directory'). It distinguishes this tool from siblings like 'read_archive_entry' and 'list_archive_entries' by focusing on bulk export with file naming and format options.

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 clear context: it exports one file per entry named by archive id, explains format options, mentions recursive directory creation, and suggests pairing with search_archives or archives_by_date_range to assemble id lists. It lacks explicit exclusions (when not to use) but the guidance is sufficient.

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