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

Annotations already declare readOnlyHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral context beyond that: what the response contains and the lifecycle rule that 'Variations stay on the cloning job until saved to the Library or scheduled.' It does not discuss rate limits or pagination, but for a read poller that is minor.

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 core information ('This returns one job...') is buried in the third sentence, behind two sentences that describe the cloning feature generally and read as belonging to clone_post. The content earns its place in context but is not front-loaded around this tool's purpose.

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 no output schema, the description correctly takes on the burden of describing the return value (status, analysed source post, variations), and read-only annotations cover the safety profile. An agent has enough to call it and interpret the result, with the only gap being the jobId's origin/format.

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%, so the description must carry the burden for the single jobId parameter. It implies the id originates from clone_post ('Poll it after clone_post'), which helps, but it never states what jobId represents or its format. This is a partial compensation, not a full one.

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 states a specific verb+resource ('returns one job: its status, the analysed source post, and every variation built so far'), which is more than the tautological title 'Get cloning job'. It implicitly separates itself from list_clone_jobs by emphasizing it returns a single job, though it does not name the sibling explicitly. The opening two sentences explain the cloning feature broadly rather than this specific tool.

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?

It gives explicit workflow guidance: 'Poll it after clone_post until status is "ready".' This tells the agent when and how to invoke it relative to clone_post. It lacks any explicit exclusion or mention of list_clone_jobs as the alternative for multiple jobs, but the context is clear.

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