Sync the applicant list of a job

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

Annotations already indicate readOnlyHint=false (mutation), openWorldHint=true, idempotentHint=true. The description adds significant context: it's a queued crawl that persists progress, resumes automatically, and includes hidden 'Not a fit' applicants by default. It also mentions that it does not open individual applications. This enriches the annotation-provided idempotence and open-world nature.

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 dense paragraph but well-organized, starting with the core action, then data fields, then behavior nuances, then exclusions, then progress tracking. While it is somewhat long, it is front-loaded with the purpose and each sentence adds necessary detail (pages, progress, alternatives). No 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?

Given the tool's complexity (queued crawl, pagination, persistence) and lack of output schema, the description explains key behaviors: chunking, progress persistence, resume, inclusion of not-a-fit, and where to check progress (queue_status/jobs_list). It also clarifies the scope (list vs details). Minor omissions might include response behavior when crawling completes, but the description is sufficient for an agent to safely invoke and monitor.

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 each parameter is described in the schema. The description adds conceptual meaning by explaining that jobId can be omitted with allJobs=true, and that pagesPerRun controls chunks of pages per worker turn. This goes beyond simple definitions and helps an agent understand relationship between parameters. However, since schema is already detailed, the added value is moderate.

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 queues a crawl of applicant lists for one or all jobs, enumerating the exact data fields (names, headlines, locations, applied dates, application ids, profile links). It distinguishes itself from applicants_fetch_details for individual applications. It doesn't explicitly name the alternative for fetching details within the main description, but does in the usage section, so it's clear enough.

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 description explicitly says 'use applicants_fetch_details for contact info, resumes and profiles' for opening individual applications, and notes that to sync every job you use allJobs=true. It also explains the pagination behavior (chunks of pagesPerRun, progress persistence, resume across restarts) guiding when to be patient. This gives clear when-to-use and when-not-to-use guidance.

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