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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description still earns credit for disclosing behavior the annotations do not: that all credentials are revoked and the action is irreversible. It does not cover auth errors or behavior on a missing job, which keeps it at 4.

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?

Three short sentences, front-loaded with the action and its consequence, with the REST endpoint in parentheses as a trailing reference. No filler; the only debatable element is the endpoint annotation, which some agents will find useful for cross-checking.

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 two-parameter destructive tool with full annotation and schema coverage, the description supplies what structured data cannot: irreversibility and credential revocation. It leaves open what happens to existing deliveries/runs and how failures surface, but nothing essential to invoking it is missing.

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 description coverage is 100%, and the schema already explains job_id format and the optional management_token/Authorization fallback. The description adds no parameter-level meaning, so the baseline of 3 applies.

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+resource ('Stop the job forever') and adds the consequential side effect ('revoke all its credentials'). The word 'forever' implicitly separates it from pause_job/resume_job, though it never names those siblings explicitly, which keeps it just short of a 5.

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?

Caution is implied by 'Cannot be undone,' and 'forever' hints at the pause_job alternative, but there is no explicit when-to-use/when-not guidance or named alternative. The agent must infer that this is the terminal option in the pause/resume/delete family.

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