Premiere text and captions

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, which the description does not contradict. However, the description adds little else about behavioral specifics, such as side effects, approval requirements (though approvalId is a parameter), or how 'advertised action' behaves. The phrase is cryptic and may confuse agents. Given annotations carry the baseline, this description adds minimal transparency.

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 short sentence, which is concise, but it is not effectively structured since it introduces an undefined concept ('advertised action') and omits needed details. It is appropriately brief but fails to prioritize the most useful information, making it less usable than it could be.

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 six parameters, nested objects, no output schema, and no parameter descriptions, this tool is complex. The description provides only a vague overview and does not explain how to specify actions, what args/target represent, or how approval works. This is far from complete for an agent to call correctly, even with annotations present.

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?

Schema description coverage is 0%, so the input schema provides no parameter explanations. The description fails to compensate: it mentions 'graphics, transcripts, and captions' but doesn't map these to any of the six parameters (actionId, args, target, approvalId, operationId, expectedRevision). An agent has no clue what actionId or args mean in this context, leaving the parameters entirely unexplained.

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 the tool 'Inspect or change graphics, transcripts, and captions', which gives a verb and resource type, but the phrase 'through an advertised action' is vague and unexplained. It doesn't clearly differentiate this from sibling tools like premiere_timeline or premiere_media, which may also involve graphics or media elements. Overall, the purpose is partially clear but not sharp enough.

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 explicit guidance is provided on when to use this tool versus alternatives. The description mentions the resource types (graphics, transcripts, captions), which implies a context, but lacks any exclusions, prerequisites, or comparisons to siblings. An agent would have no way to decide between this and other premiere_* tools without deeper investigation.

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