ass_write_timecodes

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

With no annotations to lean on, the description nonetheless discloses real behavior: output lands in workspace.output_dir, relative vs absolute path handling, the default filename, the fps fallback chain ending in a ToolError, and the meaning of the v2 flag. It omits overwrite/permission semantics and any side effects on the document, which is the main remaining 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?

Purpose is front-loaded in a single sentence, followed by cleanly structured Args/Returns sections where each line adds value. The Returns block mildly duplicates the existing output schema, a small redundancy in an otherwise tight layout.

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 four-parameter write tool with no annotations, the description covers destination, defaults, fps resolution and format selection, and an output schema exists so return values need no elaboration. Missing overwrite behavior and any note on document side effects keep it just short of 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?

Schema description coverage is 0%, so the description must carry all parameter meaning, and it largely does: path resolution rules plus default, fps resolution order, v2 default and format meaning. Only doc_id is left as a bare label ("document id"), preventing a 5.

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?

States a specific verb and resource — writing an Aegisub timecodes file — with the v1/v2 variant spelled out. It is easy to distinguish from the read-side sibling ass_read_timecodes, though the description never names or differentiates itself from siblings explicitly.

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 or when-not-to-use guidance and no reference to alternative tools such as ass_read_timecodes or ass_snap_to_frames. The fps resolution order and error note are operational detail rather than usage direction, so an agent gets no help choosing this tool over alternatives.

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