vertical_batch

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

Discloses parallel execution and a limit of 5, but no annotations exist. Missing information on safety (read-only vs destructive), authentication, error behavior, or result format. The description carries the full burden and is insufficient.

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?

Single sentence, no waste, and front-loads the key constraint. Could be slightly expanded to include return behavior without losing conciseness.

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?

The tool has one complex parameter, no output schema, and no annotations. The description does not explain return values, error conditions, or what 'vertical queries' are. It is adequate for a simple tool but incomplete for practical use.

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 coverage is 100% with a clear description of each item's structure. The description adds 'in parallel' but that is behavioral, not about parameter semantics. Baseline 3 is appropriate.

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 it runs 'vertical queries in parallel' up to 5, clearly indicating the action and resource. However, it does not use a specific verb like 'execute' or 'run', and assumes familiarity with the term 'vertical queries'.

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?

No guidance on when to use this tool versus siblings like vertical_search, search, or extract. The phrase 'via AnySearch' provides context about the backend but not about selection criteria.

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