create_template_from_file

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

Beyond the annotations, it discloses important behavior: the body is read as UTF-8 from a restricted directory, stored byte for byte, and the call fails if LISTMONK_MCP_FILES_DIR is missing or the path escapes it. This adds useful file-system and error context, though it does not describe return behavior or duplicate-name handling.

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?

Three tightly packed sentences: purpose first, use case and sibling comparison second, failure conditions third. Every sentence adds actionable information with no filler.

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 file-backed mutation tool, the description covers purpose, the inline alternative, file location constraints, encoding, and major failure modes. It lacks return-value information, but with rich schema descriptions and annotations the definition is otherwise sufficient for correct invocation.

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 the schema already documents all five parameters thoroughly. The description adds only limited semantic detail about file_path and encoding, which is useful but does not materially expand parameter meaning beyond the 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 states a specific verb and resource ('Create a template') plus the defining mechanism ('HTML body is read from a UTF-8 file'). It also distinguishes this from the sibling create_template with 'Otherwise identical to create_template,' so an agent can tell exactly what this tool does differently.

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?

It gives a clear use case ('large bodies such as MJML exports') and names create_template as the equivalent alternative. It also states prerequisites/failure conditions, but does not explicitly say when to prefer create_template over this file-based variant.

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