ass_ms_from_timecodes

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

With no annotations, the description carries the full burden. It usefully discloses the 'method' field semantics (timecodes vs fallback frame rate) and the conditional role of doc_id, but says nothing about failure modes (e.g., what happens if no timecodes file is loaded) or whether output is deterministic.

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?

Front-loaded with the core purpose, and the Args block adds value. However, the Returns block enumerates output keys that already exist in the output schema, which is redundant padding.

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 2-param conversion tool with an output schema, the description is largely adequate: it covers both params and behavioral nuances. It is incomplete regarding prerequisites (loaded timecodes) and error/edge behavior, which matter for a tool whose whole purpose depends on external state.

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 does explain that ms accepts an int/float or a time string and that doc_id is only for the fps fallback, which is meaningful beyond the bare 'Ms'/'Doc Id' schema titles, though it stops short of full compensation.

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+resource: it returns the frame containing a given ms using the loaded timecodes file. However, it does not distinguish itself from the closely-named siblings ass_frame_from_ms or ass_ms_from_frame, so an agent cannot easily tell which conversion to pick.

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?

There is one useful usage hint (doc_id is only needed for the fps fallback), but no guidance on when to prefer this over ass_frame_from_ms or ass_frame_from_timecodes, and no mention of prerequisites such as a loaded timecodes file.

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