search_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 merely repeats 'search project items' without stating whether this is a read-only query, what fields it searches, what it returns, or any side effects. It provides zero 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 a single vague sentence that does not earn its place. 'Expanded operation' is meaningless filler, and the rest is a tautology of the tool name. This is under-specification rather than concise useful information.

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 annotations, no output schema, and no parameter details, the description should clarify behavior and usage. It fails to explain what 'search' means, how it differs from the many similar sibling tools, or what value it provides to the agent, leaving the tool selection ambiguous.

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 tool has 0 parameters and an empty schema, so the baseline is 4. The description adds no parameter information, but there is nothing to document, and it does not mislead.

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 'Premiere Pro expanded operation: search project items' is essentially a restatement of the tool name and provides no additional clarity. 'Expanded operation' is vague filler, and it does not distinguish this tool from siblings like 'list_project_items' or 'find_project_item_by_name'.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention intended use cases, search criteria, or any conditions that would make this tool preferable to similar project-item query tools.

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