hires_delete_job_webhook

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

No annotations are provided, so the description should disclose behavioral traits such as irreversibility, required permissions, or error behavior. The description only states 'Delete' without mentioning any side effects or risks, leaving the agent without guidance on permanent mutation.

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?

Two short sentences, front-loaded with the action, and each phrase earns its place. No filler or redundancy.

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 tool is a deletion operation with no output schema, and the schema covers both required parameters. The description provides purpose and common use cases, but it lacks explicit warnings about permanence or clarification of the relationship between job ID and webhook ID, which could be ambiguous given the sibling tool name.

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 description says 'by ID' but does not clarify which of the two required parameters (id and webhook_id) identifies the webhook. However, the input schema provides descriptions for both parameters with 100% coverage, so the schema already handles parameter semantics; the description adds no additional meaning.

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 uses a specific verb ('Delete') with a clear resource ('job webhook subscription') and indicates the identifier method ('by ID'), distinguishing it from generic webhook deletion tools like hires_delete_webhook.

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 phrase 'Use for cleanup, rotation, and endpoint migration' provides explicit usage context for when this tool should be invoked. However, it does not explicitly distinguish from the sibling hires_delete_webhook or state when not to use it, though the 'job' qualifier implies a narrower scope.

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