deletetemplate

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

The description only says 'Delete a template', which is a simple action. However, it does not disclose any behavioral traits such as whether deletion is permanent, if it cascades to related resources (e.g., schedules using the template), or if it requires confirmation. With no annotations, the description fails to convey these important characteristics.

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 very short and front-loaded, consisting of just three words. While it is concise, it could be more informative without becoming verbose. However, for such a simple operation, it is arguably appropriately sized, but a bit more context would not hurt. Score 4 reflects good conciseness with room for slight improvement.

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?

Given the lack of output schema and annotations, the description should provide more context about what happens after deletion (e.g., success indicator, error conditions). It does not mention return values, side effects, or prerequisites. This makes the tool description incomplete for an agent to fully understand the operation.

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 has 100% coverage with the 'id' parameter described as 'Template Id'. The description adds no additional meaning beyond what the schema already provides. Since schema coverage is high, a score of 3 is appropriate; the description does not degrade or enhance parameter understanding.

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 clearly states the verb 'Delete' and the resource 'template', which is sufficient to distinguish it from sibling tools that delete other resources like device, media, playlist, etc. The input schema confirms it takes a template ID, leaving no ambiguity.

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 usage guidelines are provided. There is no mention of when to use this tool versus alternatives (e.g., gettemplatebyid for viewing before deletion), nor any prerequisites like ensuring the template is not in use or required permissions. This leaves the agent without context for appropriate invocation.

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