list_project_items

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

No annotations are provided, so the description carries the full burden. 'List' clearly implies a read-only, non-mutating operation and the recursive traversal scope is disclosed, but nothing is said about pagination behavior relative to the limit, permissions, or result shape on empty/missing bins.

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, front-loaded with the resource and followed by the two salient capabilities. No filler or redundancy.

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 could reasonably convey the shape of returned items or ordering, and it also omits any sibling disambiguation in a crowded project/timeline tool set. It is adequate for a simple read-only list call but leaves these 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 100%, so all four parameters (limit, bin_path, item_type, recursive) are already documented with defaults and an example path. The description only restates recursion and type filtering, adding no syntax or format detail beyond the schema — the expected baseline of 3.

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 names a specific verb (List) and resource scope (media, bins, and sequences in the Premiere Pro Project panel), and mentions recursive traversal and type filtering. It does not, however, explicitly distinguish itself from close siblings like list_sequences, search_project_media, or get_selected_project_items.

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?

Usage is implied by the resource being listed (project panel contents), and the recursive/filter options hint at traversal scenarios. There is no explicit when-to-use guidance or routing to alternatives such as list_sequences for sequences only or search_project_media for name-based lookup.

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