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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say the deletion is irreversible, whether a confirmation step is required, or what happens to templates referenced elsewhere.

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?

One front-loaded sentence with zero filler and the identifying forms placed after the core action. Efficient, though the extreme brevity is part of why behavioral guidance is absent.

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, irreversible tool with 0% schema description coverage and an opaque connection_context, the definition should say more about confirmation, reversibility and the context parameter. The output schema covering return values is the only gap it is excused from.

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 carries the burden. It partially compensates by clarifying that template_name accepts either a name or a public reference, but connection_context (with its mctx_v1_[0-9a-f]{64} pattern) is left entirely unexplained, and required-vs-optional is ambiguous given 0 required parameters.

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?

States a specific verb (Delete) and resource (a template), plus how the target is identified ('by name or public reference'). It is implicitly distinguishable from siblings templates_create/get/update/list, though it never names an alternative explicitly.

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 guidance on when to use this versus templates_update (to remove/modify content) or templates_list, and no prerequisites or warnings attached to a destructive operation. The only usage-adjacent information is the identifier forms, which is really parameter semantics.

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