export_audio_tool

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

With no annotations present, the description carries the full burden of behavioral disclosure. It reveals that audio is encoded to an 'export/' directory, but does not explain side effects such as overwriting files, required master state, supported formats, or what the output schema will contain. This is a meaningful gap for an export operation.

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, tight sentence with no filler, and the primary action and destination are front-loaded. However, it is somewhat under-specified in terms of parameter guidance and behavioral context, which keeps it from a 5.

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 that the tool has no annotations, two parameters, and zero schema description coverage, the description is too thin to fully support correct invocation. The existence of an output schema helps but is not shown here, and the description still omits details about format resolution, required project state, and file-writing behavior. An agent would need to infer or inspect other resources to use it 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?

Schema description coverage is 0%, so the description must compensate. It partially explains formats_json as a 'JSON override' for formats, but it does not explain the expected structure of that override or the meaning of the required project_path parameter beyond its property name. The description adds some value but leaves both parameters under-specified.

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 specific action ('Encode'), a clear resource ('mastered audio'), and a destination ('export/'), so an agent can understand the tool's basic function. It does not explicitly differentiate this from sibling export/render tools such as export_social_clips_tool or render_final, though the 'mastered audio' phrase gives useful context.

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 provides no guidance about when to choose this tool over alternatives like bounce_audio_tool, render_final, or export_social_clips_tool. It mentions configuration sources (pipeline.yaml or JSON override) but does not state conditions, prerequisites, or exclusions that would help an agent decide to invoke it.

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