engine_template_add

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states that a template group is created, which implies a mutating operation, but it does not disclose whether the operation overwrites an existing group, requires specific permissions, fails on duplicates, or what side effects occur.

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 sentence with no filler; every word carries meaning and the core action is front-loaded. This is an appropriately sized description for a simple create operation.

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 one required parameter, no annotations, and no output schema, so the description must provide enough context to call it correctly. 'Create a template group' explains the high-level purpose but omits essential details about what the 'template' parameter should contain and the behavior on existing groups, making it insufficient for safe 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?

The input schema provides no description for the required 'template' string (0% schema coverage), and the description only weakly implies that this parameter identifies the template group. It does not clarify whether 'template' is a name, path, or content payload, leaving an agent to guess the correct value format.

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 uses a specific verb ('Create') and resource ('a template group'), which identifies the operation clearly and distinguishes it from sibling tools like engine_template_rename and engine_template_remove. It does not name alternate siblings, but the resource is specific enough to avoid confusion.

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 verb 'Create' implies this tool is for adding a new template group rather than renaming or removing existing ones, but the description does not explicitly state when to use it or mention alternatives. Usage guidance is only implied, not articulated.

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