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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states 'Delete' without mentioning whether the operation is irreversible, what side effects occur on associated campaigns, or whether any confirmation or permission is needed. This is minimal coverage for a destructive operation.

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 one short, front-loaded sentence with no filler words. It efficiently communicates the action and target resource.

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 one-parameter deletion tool, the description is minimally usable: an agent knows the target and action. However, it lacks consequences, prerequisites, and any hint of reversibility, and with no output schema or annotations, this absence is not covered elsewhere.

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 input schema has 0% description coverage, and the description does not explain template_id at all. Although the parameter name is reasonably self-explanatory, the description adds no semantic value about where the ID comes from, its format, or how to obtain it from tools like google_ads_templates_list.

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 clearly states the action ('Delete') and the resource ('reusable Google ad template'), making the tool's purpose obvious. It is distinguishable from siblings like google_ads_template_update and google_ads_template_save by the verb, though it does not explicitly name those alternatives.

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 is given about when to use this tool versus alternatives, whether deletion is appropriate in certain states, or what conditions make a template deletable. The agent is left to infer usage solely from the tool name and the word 'Delete'.

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