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 of behavioral disclosure. It mentions the tool lists items but doesn't describe key behaviors such as whether it returns a paginated list, what the output format looks like, if it requires a project to be open, or any performance considerations. For a read operation with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 two sentences that are front-loaded with the core purpose and followed by usage guidance. Every word earns its place, with no redundancy or unnecessary details, making it highly efficient and well-structured.

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?

Given the tool's moderate complexity (a read operation with two optional parameters), no annotations, and no output schema, the description is minimally adequate. It covers the purpose and basic usage but lacks details on output format, prerequisites (e.g., needing an open project), or behavioral traits, leaving room for improvement in completeness.

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?

The schema description coverage is 100%, meaning the input schema fully documents the two parameters ('includeBins' and 'includeMetadata') with clear descriptions. The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline of 3 for adequate but not enhanced parameter information.

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 clearly states the verb ('Lists') and resources ('all media items, bins, and assets in the current Premiere Pro project'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'list_sequences' or 'list_sequence_tracks', which also list project components but focus on different subsets.

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 description provides clear context for when to use this tool ('to discover available media before performing operations'), which helps guide the agent toward using it as an exploratory step. It doesn't explicitly state when not to use it or name alternatives (e.g., 'list_sequences' for sequence-specific listings), but the guidance is practical and sufficient for basic decision-making.

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