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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the 'newest first' ordering and the lifecycle note that variations remain attached to a job until saved to the Library or scheduled, which is genuinely useful. It says nothing about pagination or rate limits.

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 of the three sentences describe Prolifik's product concept rather than this list tool, which is waste on a read operation, and the actual purpose is buried last. Front-loading the list behavior would make this far more scannable.

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?

With four parameters, only 25% schema coverage, no output schema, and an enum status filter, the description should explain filtering and pagination behavior. It explains neither, leaving the agent under-informed for a tool whose value lies in its filters.

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 only 25%, so the description carries the burden of clarifying limit, status, and brandId, and it clarifies none of them. Only the ordering implied by 'newest first' loosely gestures at the `before` cursor param.

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 final sentence states a clear verb and resource ('lists the account's cloning jobs, newest first'), which distinguishes it from get_clone_job. However, the purpose is back-loaded behind two sentences of product-concept framing, and it never contrasts itself with list_clip_jobs or other list_* siblings.

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?

There is no when-to-use guidance, no mention of when to reach for get_clone_job instead, and no indication of how the status/brandId filters should drive its use. The agent must infer all routing decisions 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.