batch_process

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Process multiple RAW files' without indicating side effects, required permissions, or whether files are modified. 'Process' is vague and fails to inform the agent about destructive or nondestructive 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 short and to the point, with two sentences and a parameter list. The param list is somewhat tacked on but does not waste words. It is well front-loaded with the key purpose.

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?

Despite having an output schema, the description does not mention what the tool returns (e.g., processed file paths or status). It also lacks notes on error handling, batch size limits, or performance considerations, leaving gaps for an AI agent to infer.

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 description coverage is 0%, yet the description only lists parameter names without explaining their meaning or constraints (e.g., what 'device_preset' does). It adds minimal value beyond the schema, failing to compensate for the lack of schema descriptions.

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 'Process multiple RAW files with the same PP3 profile', specifying the action and resource. It distinguishes from single-file processing tools like process_raw, but could be more precise about what 'process' entails (e.g., conversion to output format).

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 says 'Use this for bulk processing of a set of RAW files with identical settings', providing context. However, it does not explicitly mention when not to use it (e.g., for files with different settings) or point to alternatives like process_raw for individual files.

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