fusion_page_lua

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

No annotations are provided, so the description must fully disclose behavior. It only states it runs Lua code, but fails to mention whether scripts can modify the composition, what environment is used, error handling, or potential destructive effects. For a code execution tool, this is a significant gap.

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, succinct and front-loaded, but it sacrifices necessary detail. While concise, it is under-specified for the tool's complexity.

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?

Given no annotations, no output schema, only one parameter with no description, and the high complexity of executing Lua scripts, the description is woefully incomplete. It lacks behavioral traits, return information, error scenarios, and usage context.

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 has one parameter 'script' with no description (0% schema description coverage). The tool description adds no details about the script format, limits, or examples. It provides no value beyond the schema's type and name.

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 specifies the verb 'Run', the resource 'Fusion page's current composition', and a qualifier 'outside any timeline clip', making it clear what the tool does and distinguishing it from the sibling tool 'fusion_lua' which presumably runs inside a clip.

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?

The description implies when to use this tool (for Lua execution on the Fusion page outside a clip) versus the sibling 'fusion_lua' (inside a clip). However, it lacks explicit when-not-to-use scenarios, prerequisites, or alternatives beyond the implied distinction.

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