get_export_file_extension

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

With no annotations provided, the description carries the full burden. It merely says 'expanded operation' without disclosing whether the operation is read-only, what the return value looks like, or any side effects. This is insufficient for a tool that appears to be a getter.

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 front-loaded, but the phrase 'Premiere Pro expanded operation' is redundant filler that repeats the tool name without adding information. The essential content is just 'get export file extension,' so it's concise but not particularly informative.

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?

Even for a simple getter, the tool lacks an output schema, so the description should explain what the returned file extension represents and any contextual prerequisites. The phrase 'expanded operation' hints at complexity but provides no concrete details, leaving the agent without enough context to confidently invoke the tool.

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 the description doesn't need to explain parameter semantics. Per the baseline for 0 params, a score of 4 is appropriate. However, the schema allows additional properties, and the description doesn't clarify that no arguments are expected.

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 'get export file extension,' which is a specific verb+resource. However, the prefix 'Premiere Pro expanded operation' is vague and doesn't clarify what 'expanded' entails, nor does it explicitly distinguish this from sibling getters like 'get_encoder_presets.' The core purpose is clear from the name, but not enhanced.

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, what scenarios it applies to, or how it differs from alternatives. No prerequisites, exclusions, or contextual cues are provided. The description offers zero usage direction.

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