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

readOnlyHint=true already tells the agent this is a safe read, so the description is not carrying the safety burden. Beyond that it only says "recent," which vaguely implies a bounded window but never states how recent, whether results are paginated, or whether ordering is newest-first.

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?

A single short sentence with no filler, so nothing is wasted. However, the brevity comes from under-specification rather than disciplined editing, so it is only minimally adequate for a job-listing tool.

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?

No output schema exists, so the description should describe the shape of returned jobs, the recency window, and pagination or limits; it does none of these. For a tool whose main use is polling alongside wait_for_job, that leaves key operational details missing.

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 the single parameter is an optional status enum whose filtering behavior the description never explains. It does not say whether omitting status returns all jobs or only active ones, so the one free knob on this tool is undocumented in both structured fields and prose.

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?

"Recent jobs and their status." essentially restates the name and title (list_jobs / List recent jobs) without a verb or resource scope. It adds only the hint that results carry status, and gives no signal that distinguishes it from siblings such as wait_for_job or list_clips.

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 how this relates to wait_for_job (the obvious polling alternative), and no statement of when to filter by status versus listing everything. The agent must infer all routing decisions.

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