subscription_template_delete_template

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

No annotations are provided, so the description carries the full burden. 'Delete' implies a destructive mutation, but the description says nothing about irreversibility, required permissions, or the confirm:true preview behavior (that mechanism only appears in the schema, not here). For a destructive operation with zero annotation coverage this is a notable gap.

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 core sentence is front-loaded and efficient, but the inclusion of the raw HTTP path and the 'Tags: Subscription Template Controller' line adds REST-scaffolding noise without helping an agent decide or invoke correctly.

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 tool with no annotations and no output schema, the description omits the safety-relevant context an agent needs (irreversibility, confirmation requirement, side effects). The schema's confirm parameter is the only safety signal and the description does not reinforce or explain it.

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 50%: the 'confirm' parameter is documented in the schema, while 'uuid' is not. The description embeds {uuid} in the URL path, which weakly signals that it identifies the target resource, but it adds no meaning about format, source, or the confirm gate. This is the baseline level where the schema does most of the work.

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 states a specific verb+resource ('Delete subscription template') and includes the HTTP method and endpoint path, so an agent can immediately tell this apart from the sibling create/update/get template tools. It stops short of explicitly naming alternatives, which is why it is a 4 rather than a 5.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the required confirmation flow or alternative tools for managing templates. The agent is left to infer usage entirely from the name and verb.

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