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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely useful preconditions (eligible statuses), the failure case for submitted jobs, and the raw endpoint. It stops short of saying whether deletion is recoverable or what an error looks like, so it is strong but not exhaustive.

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:' then the action, the constraint, the alternative, and the endpoint in three compact clauses. Every clause carries distinct information; nothing is redundant with the title or annotations.

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 one-parameter destructive tool with full annotation coverage and no output schema, this covers almost everything needed: scope, exclusions, alternative, and endpoint. Only the failure behavior and irreversibility are unstated, which is a minor gap given the destructiveHint.

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% for the single required job_id, and the schema description already says 'an unsubmitted draft'. The description reinforces that the id must reference an unsubmitted job, which is helpful validation context but adds little beyond the schema. Baseline 3 applies when the schema fully documents the parameter.

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 (delete) and resource (job) with an explicit scope restriction: only jobs in Editing or PendingProofAcceptence status. It explicitly distinguishes itself from click2mail_cancel_job, so an agent can route correctly without opening either 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 both the when ('a job that has not been submitted') and the when-not ('Submitted jobs cannot be deleted'), plus the named alternative ('use click2mail_cancel_job'). Nothing about tool selection 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.