find_items_by_media_path

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

There are no annotations, so the description carries the full behavioral burden. It does not disclose matching semantics (exact vs substring), search scope, result format, or failure behavior; 'expanded operation' adds no concrete behavioral context.

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 short and the core purpose is front-loaded, but 'Premiere Pro expanded operation' is filler that carries little semantic weight. The sentence is concise at the expense of substance.

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 lookup tool among many sibling find/search tools, with no output schema and no annotations, this description is incomplete. It fails to explain how the media path is passed, what items are returned, and how this differs from other search operations.

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 effectively empty with additionalProperties true, providing no parameter definitions. The description references a media path but never explains how the caller should supply it as a parameter, leaving a critical invocation gap.

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 a specific action ('find'), a target ('items'), and a criterion ('by media path'). It is not a tautology and can be broadly distinguished from related tools like find_project_item_by_name, although it does not name or differentiate siblings explicitly.

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 media-path criterion implies when the tool should be used, but there is no explicit guidance about when to prefer it over alternatives like search_project_items, get_project_item_info, or find_project_item_by_name. No exclusions or decision rules are provided.

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