emails_delete_template

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's 'Delete' adds no new behavioral context. It does not mention permanence, side effects, or any other operational traits that an agent needs beyond the annotations.

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 extremely short ('Delete a template'), which is concise but under-specified. It does not include essential context such as the scope of deletion or any caveats, so it is not appropriately sized for the tool's complexity.

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 tool with a destructive action, no output schema, and 50% parameter coverage, the description is incomplete. It lacks details about what constitutes a template, how deletion affects related data, or how to distinguish from similar delete operations, leaving gaps for the agent.

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 coverage is 50% (only locationId has a description), but the description provides no parameter meanings at all. It does not explain templateId or reinforce the default behavior of locationId, leaving the agent with insufficient semantic information for the undocumented 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?

The description states the action (delete) and resource (template), but 'template' is vague without the tool name providing the 'email' context. It does not differentiate from other delete-template siblings like locations_delete_an_email_sms_template, making the purpose only moderately clear.

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 guidance on when to use this tool versus alternatives such as emails_update_template or locations_delete_an_email_sms_template. No conditions, exclusions, or selection criteria are provided.

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