ass__create_template

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

With no annotations, the description carries the full burden and does well: it states the file format (ASS v4.00+), the failure condition when the file exists (unless overwrite=true), and the output directory fallback chain. It omits return value specifics but covers the main side effects and preconditions.

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 front-loaded with the primary action and then uses a structured @remarks/@param format. Every sentence adds value—no filler—and the organization makes it easy to scan.

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 7 parameters, no output schema, and no annotations, yet the description explains defaults, style details, overwrite logic, and environment variable fallbacks. It does not describe the return value or error cases beyond the overwrite condition, but for a file creation tool this is fairly 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 descriptions are absent (0% coverage), but the description provides @param lines for all 7 parameters, explaining meaning, optionality, defaults, and fallback behavior. This is a clear addition beyond the raw schema.

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 opens with a specific verb and resource: 'Create a new ASS subtitle template file' and names the three included styles (Default, Title, Note). This is clear and distinct from sibling tools like ass__lint or ass__get_spec.

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 establishes clear context for when the tool is used (to generate an ASS template with pre-configured styles) and notes the overwrite behavior. It does not explicitly name alternatives or exclusions, but the purpose is apparent enough for an agent to choose it over siblings.

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