template_delete

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

The description lacks behavioral transparency beyond the action itself. It does not disclose whether deletion is reversible, what happens to associated resources (e.g., nodes using the template), or required permissions. Without annotations, the description carries the full burden, which it does not meet.

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 no extraneous words. However, it may be too sparse for a delete operation that likely has significant implications.

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 low complexity (1 required parameter), the description is insufficient. It does not cover return values, error conditions, or behavioral details. The presence of an output schema is not reflected in the description.

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?

With 0% schema description coverage, the description should compensate by explaining the `template_id` parameter, but it does not. The parameter meaning is implicit from its name, but no additional context is provided.

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 'Delete a template.' clearly identifies the verb (delete) and resource (template). It is unambiguous and distinguishes from sibling tools like template_create, template_get, etc.

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. The description does not specify when to use this tool versus alternatives, nor does it mention prerequisites or context such as template existence or cascading effects.

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