Delete ZeptoMail template

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

Annotations already indicate destructive and non-read-only behavior. The description adds valuable context: deletion is permanent, expected values must come from fresh reads to prevent stale operations, and confirm=true is required. This goes meaningfully beyond the structured 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?

Three short sentences with no filler. The destructive action, freshness requirement, and confirmation gate are all stated efficiently and front-loaded.

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 six parameters and no output schema, the description covers the critical preconditions: fresh reads, writes enabled, confirm=true, and explicit agent scope. It doesn't describe behavior when confirm=false or when expected values mismatch, but the essentials for safe invocation are present.

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 only 17%, so the description must compensate. It does explain that expectedAgentName, expectedTemplateName, and expectedModifiedTime must come from fresh reads, and that confirm must be true. However, templateKey is left undocumented in both schema and description, so coverage is not complete.

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 identifies the action ('Permanently delete'), the resource ('a template'), and the scope ('from one explicit Agent'). This distinguishes it from listing, getting, creating, and updating templates, even without naming a sibling.

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?

The description gives clear usage context: the tool should only be used after fresh reads, with writes enabled, and with confirm=true. It doesn't explicitly contrast with sibling tools, but the destructive delete semantics and prerequisites make the appropriate use case clear.

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