sw_batch_export

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

The annotations already flag this as non-read-only and destructive, and the description adds useful context that source files are opened read-only and never saved. It identifies the output location but does not discuss overwrite behavior or recursive traversal, which the schema partially covers.

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 a single front-loaded sentence with zero wasted text. It states the action, scope, safety context, and destination efficiently.

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 six-parameter batch export with no output schema, the description covers the core action and source-file safety but omits return/error behavior and the effects of recursive, material, and file_format. It is adequate but not fully complete.

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?

With schema description coverage at 67%, the schema already documents folder, pattern, material, and overwrite. The description reinforces folder/matching-file semantics and the output path, but adds little for material, overwrite, recursive, or file_format.

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 states a specific verb and resource: export every matching file in a folder. It also names the destination pattern, and the folder-wide batch scope distinguishes it from single-file export siblings.

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 batch nature is implied by 'every matching file in a folder', but there is no explicit guidance on when to use this instead of sw_export or when not to use it. No prerequisites or exclusions are stated.

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