Preview workflow

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

Annotations already declare readOnlyHint=true, so the description's 'safe' is redundant. However, it adds value by revealing that the output is a 'compiled UniversalVideo brief', which indicates the tool returns a processed/compiled artifact rather than a raw spec. This is useful behavioral context beyond the annotations.

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, coherent sentence that is front-loaded with the action ('Return') and resource. Every word contributes meaning, with no filler or repetition.

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 has one simple parameter, read-only annotations, and no output schema. The description explains what is returned (compiled brief) and the context (pre-render preview), which is sufficient for a basic tool. It could be more explicit about the return structure, but given the simplicity, it is adequately complete.

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 100% coverage: the only parameter jobId includes the description 'The job ID'. The tool description does not add any extra parameter semantics, such as the format or how jobId relates to the 'current workflow'. Baseline 3 applies because the schema carries the full burden.

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 clearly states the verb 'Return' and specifies the resource: 'the current workflow's compiled UniversalVideo brief'. It also includes the purpose ('safe pre-render preview'), which distinguishes it from sibling tools like inspect_workflow that likely return raw workflow data.

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 phrase 'safe pre-render preview' implies the tool is intended for previewing before rendering, but it does not explicitly state when to use it versus alternatives or mention any exclusions. No sibling tool is referenced as an alternative, so guidance is only implied.

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