collect_rsi_batch

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

No annotations are provided, so the description carries full burden. It discloses parallel execution via ThreadPoolExecutor, default workers, saving output to a directory, and target selection. However, it does not explicitly state whether the operation is read-only or if any modifications occur, nor does it mention authentication or rate limits. Overall, it is fairly transparent for a collection tool.

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 front-loaded with the core purpose and then provides structured details. It is slightly verbose (7 sentences) but every sentence adds value, especially the parameter explanations. Could be trimmed slightly but remains clear and well-organized.

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 five parameters and no annotations, the description covers target selection logic, parallel execution, defaults, output directory behavior, and config file handling. With an output schema present, return values need not be described. The description is sufficient for an agent to invoke the tool correctly without additional context.

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 0% schema description coverage, the description provides thorough explanations of all five parameters: hostnames (list), tags (AND/OR logic), output_dir (directory), max_workers (parallel threads), and config_path. The Arg block adds significant meaning beyond the input schema's bare titles, enabling correct usage.

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 tool collects RSI/SCF from multiple devices in parallel, distinguishing it from the sibling 'collect_rsi' which likely handles single devices. The verb 'collect' and resource 'RSI/SCF' are specific, and the parallel aspect sets it apart from other batch tools.

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 explains when to use the tool, how to select targets using hostnames and tags (including intersection logic), and defaults. It provides clear context for target selection without explicitly mentioning alternatives, but the sibling list supplements that. The level of detail is excellent for guiding agent usage.

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