convert_subtitles

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

No annotations are provided, so the description carries the full burden. It confirms the operation is a parse-and-transform and restates the offset semantics, but says nothing about failure behavior on unsupported/malformed input or the shape of the returned content. For a stateless transformation this is a moderate rather than severe 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?

A single tightly-packed sentence, front-loaded with the core operation and then the qualifiers. No padding or redundancy.

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?

Parameters are fully covered by the schema, but there is no output schema and no annotations, so the description should ideally say what the tool returns (converted subtitle text) and how it behaves on invalid input. As written, an agent knows what to send but not what comes back.

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 100%, so all three parameters, including the shiftMs sign convention and the toFormat enum, are already fully documented. The description only echoes the offset concept and adds no syntax or constraint detail beyond the schema, so the baseline 3 applies.

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 pair (parse and convert) and names the three concrete formats, so the purpose is unmistakable. Minor ambiguity: it says 'subtitle files' while the input is raw file content, which could mislead an agent into passing a path, though the schema corrects this.

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?

Usage is implied by the operation itself (convert subtitle content between formats with an optional offset). There is no explicit when-to-use/when-not statement, and the listed siblings are unrelated utilities so no alternatives need naming. Adequate but with no real guidance.

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