email_templates_delete

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

No annotations are provided, so the description carries full burden. The description discloses permanent destruction ('Permanently delete'), the constraint about last/default template, and the non-effect on already-sent emails. This is strong behavioral disclosure for a destructive operation, though it doesn't mention whether auth/permissions are required.

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 sentences, all carrying meaningful information with zero waste. The description is front-loaded with the primary purpose and then adds constraints and side-effect clarity. Efficient and well-structured.

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 no output schema and no annotations, the description covers the essential operational details: permanence, constraints on deletion, and non-effect on sent emails. It could mention whether the operation is idempotent or what happens with the template in active use, but overall it's fairly complete for this tool's complexity.

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 100%, with 'uuid' and 'companyId' documented in the schema. The description adds no new parameter-level detail beyond the schema. Baseline 3 is appropriate given full schema coverage.

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 verb ('Permanently delete') and resource ('an email template'), and notes the permanent/destructive nature of the action. It distinguishes this from email_templates_update and email_templates_create by making the delete-specific behavior explicit.

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 explicitly states when NOT to use the tool: 'Cannot delete the last remaining template or the default template (set another as default first)'. This gives the agent critical operational guidance for when the operation would fail and how to work around it.

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