create_job_hunt

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

With no annotations, the description carries the burden of behavioral disclosure. It states the tool creates a job hunt and its purpose, which is transparent for a create operation. However, it omits any side effects like autoMode consuming credits or that creation itself doesn't trigger applications unless configured. The schema covers these details, but the description doesn't add extra context beyond the obvious.

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?

Two sentences, front-loaded with the action, and every phrase earns its place. The first sentence states the verb and object, and the second explains what a job hunt is and its prerequisite role. No fluff.

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 the tool's complexity (nested config, many optional filters, no output schema), the description is minimal but adequate. It explains the core concept and prerequisite, but doesn't mention the default behavior of autoMode or that only titles is required in config. The schema fills these gaps, but the description alone would leave a user under-informed about the full scope.

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%, so the baseline is 3. The description mentions titles, locations, skills, salary, etc., mapping to config properties, but it doesn't add meaning beyond what the schema already provides. It provides a high-level summary but no new parameter relationships or usage tips.

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 creates a job hunt, which is a specific resource. It distinguishes from siblings like list_job_hunts, get_job_hunt, and update_job_hunt by implying this is the creation entry point. The phrase 'start tracking and applying to jobs' adds context on the resource's purpose.

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 mentions that you need at least one job hunt to use match_jobs or add_job_to_applications, providing a clear prerequisite and usage context. It doesn't explicitly contrast with update_job_hunt, but the creation role is unambiguous, so it earns a 4.

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