process_folder

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

With no annotations, the description carries full responsibility. It states that files are queued and non-recursive, but does not disclose side effects (e.g., whether it mutates state by adding jobs), permissions required, error behavior, or handling of unsupported formats. 'Queue' implies an action but leaves behavioral outcomes ambiguous.

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 sentence with no filler words. It is front-loaded with the action and resource, making it highly scannable.

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 simple tool with one parameter and an existing output schema, the description covers the primary function. It lacks notes on error conditions or prerequisites, but the core behavior is clear. Given the low complexity and presence of output schema, it is sufficiently 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?

The schema has 0% description coverage, leaving the meaning of 'path' open. The description compensates by clarifying that the path is a folder containing audio/video files. However, it does not specify path format, requirements, or edge cases. For a single parameter, this is adequate but not exhaustive.

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 uses a specific verb 'Queue' and identifies the resource: every audio/video file in a folder, with the qualifier 'non-recursive.' It goes beyond the name by specifying the file types and the non-recursive scope, which distinguishes it from sibling tools like process_audio that likely handle individual files.

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 does not explicitly state when to use this tool over alternatives like process_audio. It implies usage for folder-level batch queuing but provides no exclusions or alternative guidance. The only context is the 'non-recursive' qualifier, which informs scope but not tool selection.

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