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

With readOnlyHint=true already covering the safety profile, the description adds useful context by noting the jobs are 'latest' (recency ordering) and 'Free' (no cost). However, it does not describe pagination, ordering details, or output behavior beyond those hints.

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 description is very short and front-loads the core resource. 'Free.' is terse and potentially useful, though the overall phrasing is fragmented rather than polished.

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 simple read-only list tool with one optional parameter and no output schema, the description is still too sparse: it omits the meaning of 'limit,' ordering guarantees, and when to choose this tool over get_job. The annotations cover safety, but the description does not fill the remaining 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%, so the description must compensate for the single 'limit' parameter. It does not explain what 'limit' controls, its default, or how it interacts with returning the latest jobs, leaving the schema as the only source of type and bounds.

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 identifies the resource as the user's media jobs and implies recency with 'latest,' but it does not explicitly state the list/retrieve action or distinguish itself from the sibling get_job tool. 'Free' adds pricing context but not purpose clarity.

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 explicit guidance on when to use list_jobs versus get_job or other job-related tools. 'Latest' implies recency, but no alternatives or exclusions are named.

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