search_jobs_bulk

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: internal parallel search, results saved to a file, and response containing a summary and file path. It also instructs the user to read the file for details. Minor gaps remain, such as file persistence and error handling for invalid inputs, but overall transparency is strong.

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 compact yet comprehensive. It front-loads the purpose, then explains the process, output, and usage guidance in a logical order. Every sentence adds value, with no fluff or redundancy.

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?

Despite no output schema, the description explains the return format (summary and file path) and the side effect of file creation. The tool has only 2 parameters, and the description provides enough context for an agent to invoke it correctly, including use case and performance benefit.

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 100%, with both company_names and platform having clear descriptions. The tool description adds minimal parameter-specific detail beyond what the schema already provides, so the baseline of 3 is appropriate per the rubric.

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 'Search job postings for multiple companies at once' with a specific verb and resource. It distinguishes from the sibling tool search_jobs by emphasizing bulk search and speed advantage, making its unique purpose unambiguous.

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?

Explicitly states when to use: 'Use this when you want to look up many companies at once, such as a list of companies designated for military exemption.' It also directly compares to the alternative: 'much faster than calling search_jobs multiple times,' providing clear guidance on tool selection.

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