bulk_advance

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

With no annotations, the description takes on full responsibility. It clearly states 'Write operation — rate-limited' and 'Processes sequentially with rate-limit delays,' which are critical behavioral traits. It doesn't mention permission requirements or partial failure behavior, but the key operational constraints are disclosed.

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 and front-loaded: purpose, critical warning, practical usage, and optional parameter logic—all in three sentences with no wasted words. Every sentence adds value.

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 (bulk operation, optional filtering, rate limits) and the presence of an output schema, the description adequately covers what an agent needs: how to identify target applications, when to use from_stage_id, and the sequential/rate-limited execution. It could mention error handling or what happens if some applications are invalid, but that's a minor gap given the schema's output coverage.

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%, but the description adds significant meaning: it tells users to get application_ids from pipeline_summary or list_applications, and explains that from_stage_id should be matched by name via list_job_stages_for_job. This is practical workflow knowledge beyond the schema's field descriptions.

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 opens with 'Advance multiple applications to the next stage,' a specific verb+resource combination. The word 'multiple' distinguishes it from the sibling tool advance_application, which handles single applications.

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?

It provides clear guidance on when to use: includes a natural-language trigger ('move everyone past phone screen forward'), tells users where to get application_ids (pipeline_summary or list_applications), and how to optionally filter by stage using list_job_stages_for_job. It doesn't explicitly say 'use advance_application for a single application,' but the bulk semantics make it clear.

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