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

With no annotations, the description carries the full burden: it usefully discloses sort order (newest first), default scope (all jobs in a project unless filtered), and the key semantic that outputAssetIds are the produced results. It is silent on pagination/limits, whether jobs still in progress appear, and what an empty outputAssetIds means — meaningful gaps for a list tool with zero annotation coverage.

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 tight sentences with the purpose and scope front-loaded and zero filler. The long parenthetical job-type list and the appended sentence about outputAssetIds are dense but each carries information an agent needs.

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 read-only listing tool with five undocumented parameters, no annotations and no output schema, the definition covers purpose, ordering, filter scopes and the meaning of outputAssetIds reasonably well. It remains incomplete on pagination, on the structure of returned job entries, and on the required/single-projectId constraint.

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 coverage is 0%, so the description must supply meaning, and it does partially: it assigns shotId, characterId, locationId and placeholderId to their filter scopes (with "music/voice placeholder" clarifying placeholderId). It never states that projectId is required or whether multiple filters are mutually exclusive or intersecting, leaving real ambiguity for a 5-parameter tool.

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 opens with a specific verb+resource ("List generation jobs") and enumerates the job kinds it covers (character views, location plates, keyframes, takes, lip-sync/revoice, music, voice lines), which separates it in practice from generation.status and generation.cancel. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than stated.

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 conveys when to use the tool (retrieve a project's job history, optionally narrowed by shot, character, location or placeholder) and notes the newest-first ordering, which implies a history/harvest use case. There is no explicit guidance on when NOT to call it versus generation.status, nor on whether filters can be combined.

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