admin_injects_delete_template

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

The description notes that only white team members can delete templates, which is a useful access constraint. However, it does not disclose that deletion is likely irreversible or describe any side effects (e.g., removal from related injects), and there are no annotations to compensate.

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 two short sentences, front-loaded with the action and immediately followed by the access restriction. Every word earns its place; no fluff or redundancy.

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 simple delete operation with one fully documented parameter, the description is adequate but could mention that deletion is permanent and what happens to associated data. Without annotations, it misses an opportunity to warn agents about irreversible consequences.

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 single parameter template_id is fully documented in the schema with 100% coverage. The description adds no extra semantic detail beyond confirming the context, so it meets the baseline but does not 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 uses the specific verb 'Delete' with the resource 'inject template', clearly distinguishing it from sibling tools like create, update, or get templates. The white-team-only note further clarifies its scope.

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 explicit guidance is given for when to use this tool versus alternatives such as admin_injects_update_template or admin_injects_create_template. The action itself implies usage, but there are no exclusions or references to other tools.

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