vfx3d

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

No annotations exist, so the description carries the full behavioral burden and discloses nothing: not whether operations are read-only or mutate the project, not whether they are reversible, not what permissions or render dependencies exist. The keyword list conveys zero behavioral context.

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 scannable, with the domain keywords front-loaded. But it is a bare noun list with no verb or dispatch structure, and the bracketed '[15 actions]' is metadata noise rather than useful information.

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?

For a complex multi-action dispatcher over a nested args object, with no annotations and no output schema, the description is nowhere near complete. An agent cannot determine the valid action values, the arg shape, or the effect of any operation from this text.

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% for both parameters, and the nested 'args' object is entirely undocumented. The description neither explains that 'action' selects one of 15 operations nor hints at what 'args' must contain, so it fails to compensate for the coverage 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 names a topical domain — 3D scenes, lights/materials, relight, particles, shard bursts, fracture glass — so an agent can tell it apart from siblings like color_grade, audio or tracking. However, there is no verb and no statement of what the tool actually does (create, apply, render?), and it never says it is a 15-action dispatcher. It reads as a keyword bag, not a purpose.

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 when-to-use, when-not-to-use, or alternative is given. Borderline cases with the effects, graphics and masks siblings are unaddressed, and the '[15 actions]' hint signals a dispatcher without ever naming the actions that would let an agent choose this tool over another.

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