get_qe_clip_info

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It does not state whether the operation is read-only, what data it returns, or whether it has any side effects on the Premiere Pro state.

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 under-specified rather than concise. The phrase 'Premiere Pro expanded operation' adds no information and the remainder restates the tool name. The single sentence does not earn its place as it conveys almost nothing.

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 a vague description, the tool is completely under-described. The agent has no way to know what 'qe clip info' refers to, what the return value is, or how to use it effectively among the large set of sibling tools.

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?

With 0 parameters, the baseline is 4 according to the scoring rules. The schema is trivially covered (100%), and the description adds nothing about parameters, but no parameter explanation is needed given there are none.

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: get qe clip info' is essentially a tautology of the tool name. It does not explain what 'qe' means, what clip info is retrieved, or how it differs from sibling tools like get_full_clip_info or get_clip_properties.

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 vs alternatives. The description offers no context about prerequisites, selection requirements, or typical use cases, leaving the agent with no basis for tool selection.

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