delete_template_entity

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

With no annotations, the description carries the full burden, and it does usefully disclose a side effect beyond the deletion itself ('reloads template domain'). However, it omits whether deletion is irreversible, what happens if the named entity does not exist, and any permission requirements.

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 tight sentence with the action front-loaded and the side effect parenthesized at the end. Nothing is wasted, though the parenthetical is slightly cryptic about what 'reloads template domain' entails.

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 destructive, annotation-free tool with two undocumented parameters and no output schema, the description covers the essential action and one side effect but leaves irreversibility, error behavior, and permissions unstated.

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 schema contributes nothing beyond names and types. The description partially compensates by indicating that template_type and name together form the identifying key, but it adds no format, valid values, or case/whitespace semantics.

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?

Specific verb + resource ('Delete a template entity') with identifying keys ('by type + name'). It is distinguishable from siblings like delete_automation and delete_helper by name, but it never explicitly frames itself against the template-entity family (upsert/list/get_template_entity).

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?

No when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives. The only guidance is implicit in the name — an agent must infer that this is the removal counterpart to upsert_template_entity.

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