find_items_by_media_path

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

There are no annotations to provide safety or side-effect information. The description 'Premiere Pro expanded operation: find items by media path' gives zero behavioral detail—no return format, no side effects, no error conditions, no dependencies. It's essentially a restatement of the tool name with the word 'expanded' added, offering no transparency beyond what the agent can infer from the name.

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 a single short sentence with no wasted words. However, it's minimal to the point of being nearly useless—'expanded operation' adds nothing, and there's no structure or front-loaded critical info (like required input or output). Brief but not helpful.

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 zero documented parameters)Skip this. The tool clearly requires some kind of path argument, but neither the schema nor the description explains how to supply it. There are no annotations, no output format, no edge cases, and no differentiation from sibling find_project_item_by_name. The agent gets essentially no actionable guidance.

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 input schema is essentially empty (0 parameters, propertyNames allows arbitrary strings, no defined properties). The tool clearly needs a media path input, but the description provides zero guidance on what parameters to pass or their format/types. With 0 documented params and the description not mentioning any inputs, the agent has no way to correctly invoke this 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 states 'find items by media path', which clearly indicates the action (find) and the resource (items) plus the filter criterion (media path). However, it adds 'expanded operation' which is vague jargon, and it doesn't differentiate from the sibling find_project_item_by_name or search_project_items, both of which could also find items. Purpose is clear but not distinctive.

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?

No guidance on when to use this tool versus alternatives. There are many sibling tools that find or search items (find_project_item_by_name, search_project_items, get_all_project_paths), yet the description gives no context for when this is the right choice. No exclusions or comparisons are mentioned.

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