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

Annotations already indicate this is not read-only but not destructive; the description adds nothing beyond the operation itself. It does not disclose whether users are appended or replaced, whether duplicates are allowed, whether the job must be in a draft state, or any effects on an already-running job.

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, front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of behavioral and workflow context.

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?

For a simple two-parameter mutation with no output schema, the description is minimally adequate, especially since the schema covers both parameters. It omits the lifecycle relationship with create_bulk_job/run_bulk_job and any constraints, leaving an agent to guess the intended workflow.

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?

Input schema coverage is 100%, with descriptions for both job_id and users, so a baseline of 3 applies. The description adds no additional parameter semantics beyond restating that users are added to an existing job.

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 states a clear action ('Add users') and the target resource ('an existing bulk job'), which distinguishes it from creation and execution tools such as create_bulk_job and run_bulk_job. It does not, however, clarify what a 'bulk job' is or how this differs from list/tenant/user bulk operations, leaving some ambiguity.

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 word 'existing' conveys that this must be used only after a bulk job has been created, which is an implicit usage condition. No alternative tools or when-not-to-use guidance are provided, so an agent must infer placement in the create→add→run workflow from the sibling names.

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