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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description goes beyond that by specifying the scope of destruction: unsaved variations live on the job and are removed, while variations already saved to the Library survive. That is exactly the kind of consequence detail an agent needs before a destructive call.

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?

Roughly 75% of the text is preamble about the cloning product rather than this tool. For a single-parameter delete, the relevant content ('This deletes the job. Variations already saved to the Library survive it.') is two sentences buried at the end instead of front-loaded. The marketing copy does not earn its place in a delete tool's definition.

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-param destructive tool with no output schema, the description covers the key data-loss consequence, which annotations alone would not. It omits permission/auth requirements, whether the job record itself is recoverable, and how to obtain a valid jobId, leaving modest 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?

Schema description coverage is 0% and there is one parameter (jobId), so the description carries some burden. It refers to 'the job' and 'the cloning job,' which implicitly identifies what jobId targets, but adds no format, sourcing, or lookup guidance (e.g., obtain via list_clone_jobs or get_clone_job). Marginal compensation for the coverage gap.

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 actual purpose is stated plainly in sentence four: 'This deletes the job.' However, three of the four sentences describe the cloning feature generally (pasting TikTok/Instagram links, generating variations), not the delete operation, so the purpose is buried under product marketing rather than front-loaded. There is also no differentiation from the delete-adjacent siblings (retry_clone_job, distribute_clone_job).

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 never says when to delete a job versus when to retry or distribute it, nor any prerequisite or caution condition. The statement that saved variations survive is useful consequence information, but it is not usage guidance for selecting this tool.

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