bulk_format

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal that the operation queues items, uses parallelism, and has optional ATS-safe and multilingual features. However, it does not explain what the output is (e.g., a job ID), whether the operation is asynchronous, or any side effects, leaving notable gaps.

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 that front-loads the action and packs important details. The parenthetical 'mirroring Bullhorn/JobAdder/Vincere search-result batches' adds specificity but could be trimmed without losing core meaning, so it is concise but not maximally lean.

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 description covers the purpose and high-level options but does not mention the expected return value, the potential need to poll get_job_status, or any prerequisites like authentication or prior caching. Given the absence of an output schema and annotations, these omissions make the description only minimally complete for a batch operation.

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 provides zero descriptions for parameters, so the description must compensate. It explains that cv_ids are 'cached CV identifiers,' template_id is for 'a single branded template,' and options cover 'ATS-safe typography and multilingual coverage,' adding meaningful context beyond the raw schema.

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 a specific action: queueing cached CV identifiers for parallel formatting against a single branded template. It distinguishes itself from siblings like format_cv (singular) and tailor_cv (customization) by emphasizing bulk operation and the use of a shared template.

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 phrase 'dozens of cached CV identifiers' and 'parallel formatting' clearly imply this is for bulk formatting tasks, providing useful context. However, it does not explicitly mention when not to use it or name alternatives, such as using format_cv for single CVs, so it does not fully meet the explicit-usage criterion.

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