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

Annotations already declare this a safe, idempotent read, so the safety profile is covered. The description does add one useful behavioral fact — the response includes rendered clips, not just a status string — but says nothing about status values, terminal states, or how often to poll.

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?

One short, front-loaded sentence with zero filler, which suits a simple one-parameter lookup. It leans toward under-specification rather than padding, but nothing in it is wasted.

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?

There is no output schema, so the description carries the return-value burden, and it does name the two things returned: status and rendered clips. Missing are the possible status values and the form of the rendered clips, but for a one-parameter read tool with readOnly/idempotent annotations this is close to sufficient.

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 single required job_id has no documentation at all in the schema. The description only implies that job_id identifies a clip job; it doesn't explain where the ID comes from (presumably a create call's response) or its format.

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 and resource: fetch a clip job's status plus rendered clips. It is clearly distinct from siblings like clipwright_create_clips or clipwright_check_rights, though it never names an alternative to sharpen that boundary.

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 card gives no when-to-use guidance, no mention of polling after clipwright_create_clips, and no indication of when the job is finished versus still running. The purpose is inferable from the sentence, but nothing in the text tells an agent when to reach for this tool over its siblings.

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