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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered upstream. The description adds nothing beyond that—no note on permanence, on what happens if the template is still used by links, or on behavior for a nonexistent ID—so it earns little credit beyond the structured fields.

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 short sentence, front-loaded with the action and resource, with no filler or repetition of the title. It is appropriately sized for a single-parameter delete, though it leaves little room for the context a destructive operation warrants.

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?

The schema is complete and annotations carry the destructive/idempotent profile, and no output schema is needed for a delete. However, for an irreversible operation the description omits error semantics (unknown ID, template in use), which is the remaining gap an agent would care about.

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 100% and the single parameter (template_id) is documented in the schema itself. The description only names "by its ID" and adds no format, source, or lookup guidance, so baseline 3 applies.

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 and resource ("Delete a saved UTM parameter template") plus the identifier used to do it, so the action is unambiguous. It does not distinguish itself from siblings such as create_utm_template or list_utm_templates, but the verb-resource pairing is clear enough on its own.

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 when-to-use guidance is given: nothing says whether to delete versus recreate, whether the template must be unreferenced by existing links, or what to do when the ID is unknown. The only routing signal is the verb itself.

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