get_full_clip_info

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

With no annotations, the description carries the full burden of disclosing behavior, but it is completely silent on what the tool returns, whether it performs any side effects, which clips it operates on, or any errors that may occur. 'Get full clip info' gives no behavioral detail beyond the obvious.

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 sentence but is under-specified and tautological. It conveys no actionable information, so it fails to earn its place as a useful description despite being short.

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?

This tool likely returns complex clip data, yet there is no output schema, no annotations, and no description of return values or behavior. The description is fundamentally inadequate for an agent to understand what information is returned or how to interpret it.

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 zero parameters, so there is no parameter list to describe. The schema is open and uninformative, but since no parameters are expected, the description does not need to elaborate. The baseline for 0 params is 4, and no deduction is made.

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 essentially restates the tool name: 'get full clip info' adds no new specificity beyond the name itself. The phrase 'Premiere Pro expanded operation' does not clarify what qualifies as 'expanded' or what differentiates this from sibling tools like get_clip_properties or get_item_info.

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 is provided about when to use this tool versus alternatives. There is no mention of prerequisites, selection requirements, or scenarios where this tool is preferred, making it impossible for an agent to decide when to invoke it.

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