get_email_template

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

No annotations are present, so the description carries full burden. It states the output includes HTML body and variables schema, but does not disclose whether the operation is read-only, what happens on error (e.g., slug not found), or any authentication or rate limits. For a read operation, minimal behavioral context is provided.

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 a single sentence, front-loads the purpose, and includes key details. However, it could incorporate context for the project_id parameter without becoming verbose. Efficient but slightly terse.

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 simple get operation with two parameters, the description adequately states the action and output. However, it lacks explanation for the required project_id parameter and does not specify the return format of the 'variables schema'. Missing output schema increases the need for description completeness.

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?

The description reinforces that slug is the identifier, but does not explain the purpose of project_id, which is required and has no description in the schema. With schema coverage at 50%, the description only partially compensates by clarifying slug's role.

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 action (Get), the resource (email template), selection method (by slug), and what is included (full HTML body and variables schema). This distinguishes it from siblings like list_email_templates which returns a list, and preview_email_template which likely only shows a preview.

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 implies usage for retrieving a single template by slug, but does not explicitly state when to use this vs siblings like list_email_templates or preview_email_template. No guidance on when not to use or alternative tools is provided.

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