hires_create_email_template

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

No annotations are provided, so the description must disclose side effects and nuances. It does disclose that placeholders require a multi-step preparation process, and that subject and body support placeholders. However, it does not mention required permissions, idempotency, duplicate name handling, or what the API returns upon creation. The description also confusingly says placeholders like {{first_name}} are supported but then instructs to get an HTML tag from prepare, leaving ambiguity about the exact placeholder syntax.

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 three sentences: a clear purpose statement, a note about placeholder support, and a numbered list for the placeholder workflow. It is front-loaded with the main action first, and every sentence contributes useful information without padding.

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?

The tool has 4 parameters with full schema coverage and no output schema. The description covers the main purpose and the trickiest aspect (placeholder embedding), but omits details about the created object's return value, whether company_id is optional or required for multi-tenant scenarios, and edge cases like duplicate names. Given the simplicity of a create operation, it is reasonably complete but not exhaustive.

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 descriptions cover all 4 parameters, so the baseline is 3. The description adds value beyond the schema by explaining that subject and body support placeholders and by giving a workflow to generate the correct HTML tag. It does not add meaning for name or company_id, but the existing schema descriptions are adequate.

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?

Clearly states it 'Create a new email template with name, subject, and body'. This is a specific verb (create) plus resource (email template), distinguishing it from sibling tools like update_email_template and delete_email_template. It also mentions the key feature of placeholder support.

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 usage instructions for embedding placeholders, referencing GET /template-placeholders and POST /template-placeholders/prepare as required preliminary steps. This gives the agent a concrete workflow for a common task, and implicitly indicates that placeholders require two additional calls before insertion. However, it does not explicitly contrast with update/list/delete tools, though the create semantics are clear from the name.

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