save-template

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

With no annotations, the description discloses that the tool writes to an on-disk store (APPLE_MAIL_MCP_TEMPLATES_FILE), persists across restarts, and overwrites existing templates when an id is provided. It notes placeholders in subject/body. Minor omission: no mention of behavior for invalid id or id generation for new templates.

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 concise, front-loaded with the primary use case, followed by return value, exclusions, and safety details. Every sentence adds value with no redundant 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 6 parameters and an output schema (not shown but referenced), the description covers creation, update, return format, alternatives, and persistence. Missing details: how new templates get an id, error handling for invalid ids or duplicate names.

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?

While schema coverage is 50% (descriptions for cc, id, to only), the description compensates by explaining the role of id (updating), and that subject/body may contain placeholders. However, it does not elaborate on allowable placeholder syntax or constraints beyond the schema.

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 tool creates or updates reusable email templates, specifying the components (name, subject, body, optional to/cc). It distinguishes from sibling tools like create-draft and send-email via explicit 'Do not use when' guidance.

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?

Provides explicit 'Use when' and 'Do not use when' sections with specific alternative tool names (create-draft, send-email, use-template). Also clarifies updating by passing an existing id.

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