enterprise_collect_batch

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

No annotations are provided, so the description must carry the full behavioral burden, but it discloses none: no side effects, duration, rate limits, auth requirements, or meaning for parameters like checkpoint_path and stop_on_blocked. It only describes the input separator format.

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 single sentence is front-loaded and wastes no words, but it is too sparse for a 7-parameter tool and omits information an agent needs in order to invoke it correctly.

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 complex 7-parameter batch collection tool with no annotations and 0% schema description coverage, the description is far too incomplete. The output schema helps with return values, but the description still omits routing, behavior, and six of seven input parameters.

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% across 7 parameters. The description explains only the required keywords parameter's separator format, leaving depth, fields, platform, persona_id, checkpoint_path, and stop_on_blocked completely undocumented.

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: 'Collect multiple company keywords.' The word 'batch' in the tool name and 'multiple' in the description clearly indicate multi-keyword scope, but it does not explicitly distinguish this from the sibling enterprise_collect tool.

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?

There is no guidance on when to use this tool versus enterprise_collect, enterprise_search, or other siblings. The only implied usage is bulk keyword input, with no prerequisites, exclusions, or routing context.

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