Remove Template

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

No annotations are provided, so the description carries full burden. It discloses that removing a template is irreversible and requires user double-check. While additional details (e.g., on success response) could be included, the key behavioral trait of irreversibility is clearly stated.

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 two sentences, front-loaded with the action ('Remove an email template...'), followed by critical usage guidelines. Every sentence serves a purpose, with no superfluous information.

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?

Given no output schema, the description covers all necessary aspects: what the tool does, how to identify the template, and the crucial prerequisite of user confirmation. It is complete for a deletion tool.

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?

There is only one parameter 'id' with a schema description covering 100% of parameters. The description does not add new meaning beyond the schema's explanation of what the ID can be (ID, alias, or URL). Baseline 3 is appropriate as the schema already documents the parameter adequately.

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 'Remove an email template by ID, alias, or Resend dashboard URL from Resend.' The verb 'Remove' and resource 'email template' are specific, and the tool is clearly distinguishable from sibling removal tools that target different resources.

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 provides explicit guidance: 'Before using this tool, you MUST double-check with the user...' and 'You may only use this tool if the user explicitly confirms...' This clearly states when and how to use the tool, including the prerequisite of user confirmation.

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