bdesign_editor_render

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

Annotations only cover idempotency and destructiveness (both false). The description adds valuable context about the ffmpeg/ffprobe dependency, which is a runtime prerequisite. It does not disclose other important behaviors such as whether the render is synchronous or asynchronous, whether it mutates project assets, or what happens on failure. The added dependency is useful but does not fully close the behavioral 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 two terse sentences. The first defines the core action and output; the second provides a critical dependency. Every word earns its place, with no redundancy or fluff.

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?

There is no output schema and no enrichment for parameters, so only the basic purpose is declared. For a side-effecting render operation the agent would need to know what a successful call returns (e.g., asset ID), how expectedRevision is used, and error expectations. The description is under-specified for an agent to call the tool reliably.

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?

Input schema has zero parameter descriptions (0% schema coverage), so the tool description must explain the parameters. It does not mention projectId or expectedRevision at all. "Project-owned" only implies projectId, but expectedRevision is left entirely unexplained (likely a concurrency or revision token). The description fails to compensate for the total lack of schema parameter documentation.

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 a highly specific verb ("Render") and resource ("authoritative Editor timeline to a project-owned MP4 Asset"), plus concrete output features (overlays, captions, mixed audio). This clearly distinguishes it from siblings like bdesign_editor_view or bdesign_editor_snapshot, which are not rendering final MP4 assets.

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?

It tells the agent this produces the authoritative MP4 and makes a required runtime dependency explicit (local ffmpeg and ffprobe). However, it does not explicitly say when to use it versus siblings (e.g., final export vs preview/snapshot), nor provide any clear exclusions beyond the ffmpeg requirement.

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