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

The annotations already signal destructive behavior (destructiveHint=true, readOnlyHint=false). The description adds the purpose of alignment across integrated platforms, which implies potential side effects beyond local deletion. However, it does not disclose specifics like whether the deletion is permanent, whether it affects related entities, or any authorization requirements. With annotations present, the description provides marginal additional transparency.

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 extremely concise with only two sentences, front-loading the primary action. Every word adds value, with no redundancy or filler.

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?

The description clearly states the tool's purpose and provides context for its use. For a simple delete operation with one parameter and annotations signaling destructiveness, the description covers the essential information. A minor gap is that it does not explicitly state whether the deletion is permanent or reversible, but the destructiveHint annotation compensates.

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?

The input schema already fully documents the single parameter with a description ('Job ID (numeric) or alias'). The tool description does not add any additional semantic information beyond what is provided in the schema, so the parameter semantics are adequately covered by the schema.

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 explicitly states the action ('Delete') and the resource ('a job'), making the primary purpose unambiguous. It further clarifies usage for synchronizing archived/removed positions across integrated platforms, differentiating it from other deletion tools (e.g., hires_delete_application) and from job-related tools like update or create.

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 provides context on when to use this tool ('to align archived/removed positions across integrated platforms'), which implies a synchronization use case. However, it does not explicitly state when not to use it or contrast with alternatives like setting job status or using other deletion tools, leaving some ambiguity.

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