engine_template_rename

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It only states the obvious rename action, without mentioning side effects, reversibility, permissions, or what happens to associated data. For a mutation tool with no annotation support, this is insufficient.

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 concise and front-loaded with the core purpose in a single sentence. However, it is arguably under-specified, but for a simple tool, the brevity is acceptable. The structure is clean, though it could benefit from a brief parameter note.

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 tool with two required parameters, no output schema, and no annotations, the description is incomplete. It does not explain parameter semantics, potential side effects, or how it fits into the broader toolset. An agent would struggle to invoke it correctly without additional inference.

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 explain the two parameters (was_template and new_template). It does not. The parameter names are somewhat self-explanatory, but the description adds no meaning beyond what the schema provides, failing to compensate for the coverage gap.

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 clear action (rename) and resource (template group), which is specific and easily understood. However, it does not differentiate from the many sibling rename tools (e.g., engine_html_rename, engine_static_rename), though the name itself provides some distinction. Without explicit sibling differentiation, it's a solid 4.

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 no guidance on when to use this tool versus the other rename tools or any alternatives. It does not mention prerequisites, typical use cases, or conditions that would select this tool over siblings. With many similar tools available, this is a significant gap.

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