evaluate_expression

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention side effects, return values, permissions, or any operational details, leaving the agent entirely in the dark.

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 one sentence, but it is under-specified rather than concise. It merely rephrases the tool name and provides no informative content, so it does not earn its place.

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?

The tool lacks an output schema and annotations, and the description is a single tautological phrase. For a tool that likely handles arbitrary expressions, there is no information about inputs, outputs, or behavior, making it completely inadequate for an agent to invoke correctly.

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 schema defines 0 parameters, and the description adds no parameter detail, but the baseline for 0 params is 4. However, the schema allows arbitrary properties (propertyNames/additionalProperties), and the description does not clarify whether any arguments are expected or how to pass an expression, which is a slight gap.

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: evaluate expression' is essentially a tautology, restating the tool name without explaining what the expression evaluation does, what types of expressions are supported, or the outcome. It does not distinguish this tool from similar siblings like execute_extendscript or inspect_dom_object.

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 on when to use this tool or when to prefer an alternative. There is no mention of context, prerequisites, or exclusions.

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