delete_template

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

The annotations already disclose that this is destructive, idempotent, not read-only, and open-world, so the description adds little behavioral context. It does not explain what else may be affected by deleting a template, whether deletion is reversible, or what permissions are required.

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 short and front-loaded, with the operation stated first and the endpoint second. It is efficient, though the endpoint path mostly restates the parameter names rather than adding much explanatory value.

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 operation with no output schema, the description is too thin. It omits side effects, permissions, confirmation expectations, and the consequences of deleting a template, leaving the agent with only the endpoint and verb.

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 carry the burden for parameter meaning. It only repeats project_id and template_id as URL path placeholders and adds no explanation of what those identifiers select or any constraints beyond the schema's integer minimum.

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 gives a specific verb and resource: 'Removes template', and reinforces it with the DELETE endpoint path. It is clear what the tool does, though it does not explicitly differentiate itself from nearby destructive siblings such as delete_template_permission or detach_template_inventory.

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 description provides no guidance on when to use this tool versus alternatives, no prerequisite checks, and no warning about confirming a destructive template deletion. The operation is implied only by the verb 'Removes'.

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