bulk_advance

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

With no annotations, the description carries the full behavioral burden and does so: it declares this is a write operation, that it is rate-limited, that processing is sequential with rate-limit delays, and enumerates the skip rules (rejected/hired/prospect apps, and apps not currently in from_stage_id).

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?

Front-loads the operation and its write/rate-limit nature, then adds usage, mechanics, and edge cases in compact sentences with no filler. Every sentence conveys a distinct fact an agent needs.

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?

Both parameters are documented, an output schema exists so return values need no explanation, and the description covers the mutation semantics, rate limiting, and skip behavior for a bulk write tool with no annotations.

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, but the description goes further by explaining the skip consequence of from_stage_id ('others are skipped'), how to derive it (list_job_stages_for_job, match by name), and where to obtain application_ids, which the schema does not say.

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?

States a specific verb (advance), resource (applications), and scope (multiple / bulk) in the first clause, which cleanly separates it from the single-application sibling advance_application. It also names the exact state transition: each app moves to the next stage on its job's interview plan.

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?

Gives concrete routing for inputs ('Get application_ids from pipeline_summary or list_applications'), a real user phrasing that triggers it, and a clear condition for when to use from_stage_id. It never explicitly says to use advance_application for a single app, but the bulk framing and the source-tool pointers cover the practical decision.

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