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

The description adds no behavioral context beyond what annotations already provide. Annotations include destructiveHint=true, and the description says 'Delete', which aligns but adds nothing new. It does not mention permanence, side effects, or prerequisites. With annotations covering the destructive nature, a score of 2 reflects the lack of 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 a single sentence and is extremely concise. It is front-loaded and easy to parse. However, it is so terse that it sacrifices valuable information that could fit without bloat, so it is not perfect.

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 delete tool, the description is insufficient. It lacks usage guidance, parameter semantics, and behavioral context beyond the action. An agent would not know the relationship between 'id' and 'webhook_id' or any consequences of deletion. The absence of an output schema and the minimal description leave important gaps.

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 schema description coverage is 50%, with only 'id' documented as 'Job id or alias' and 'webhook_id' having no description. The tool description does not explain either parameter, so it fails to compensate for the missing webhook_id semantics. The name hints at webhook_id being a webhook identifier, but that is implicit.

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 'Delete a job webhook' clearly states the action (delete) and the resource (job webhook). It is specific enough to distinguish from general webhook tools like hires_delete_webhook, though it doesn't explicitly call out that distinction. The purpose is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention that this is for job-specific webhooks, nor does it reference sibling tools like hires_delete_webhook or hires_rotate_job_webhook_secret. An agent would have to infer usage from the name alone.

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