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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: no message is sent to candidates and the write is a pure association on the job's pipeline, plus the POST endpoint. It does not say what happens when a candidate is already in the pipeline or when some ids in the batch are invalid.

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-loaded with 'WRITE:' and packed into one dense sentence-plus-parentheticals with no filler. The nested asides make it slightly harder to scan than a clean two-sentence structure, but every clause carries information.

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 3-parameter mutation with no output schema, the description covers what it does, its non-obvious semantics and its location nuance. The remaining gap is outcome behavior, i.e. batch partial-failure handling and whether already-associated candidates are silently ignored (implied only by idempotentHint).

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% and all three parameters are documented in-schema, so the baseline is 3. The description's only parameter content, the location_id rule, restates the schema's 'only for a job with several locations' almost verbatim, adding no new syntax or format detail.

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 and resource ('associate existing candidates to a job') plus the effect ('appear in its recruitment pipeline'), and preempts the most likely confusion by saying this is a recruiter association, not a candidate application. An agent can distinguish it from taleez_create_candidate and the pool variant without opening a schema.

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 a concrete conditional instruction ('Pass location_id for a job with several locations') and clarifies the semantics of the operation (recruiter association, no message sent), which tells the agent when this is the right call versus its siblings. It never names taleez_add_candidates_to_pool explicitly as the alternative, so the job-vs-pool routing is left to inference.

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