hires_prepare_template_placeholders

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core transformation without mentioning side effects, failure modes, prerequisites, or whether the operation is read-only. This is minimal transparency for a tool with no structured safety hints.

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, well-structured sentence that communicates the core purpose without any superfluous information. It is appropriately sized and front-loaded.

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?

With 6 parameters, no annotations, and no output schema, the description is insufficient. It does not explain which parameter combinations are valid for each placeholder type, nor does it describe the HTML tag format or return value. This leaves significant gaps for an agent to use the tool correctly.

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%, so the baseline is 3. The description does not add any detail about how parameters like job_variable_id or system_column_title relate to the placeholder 'type' field, but the schema already provides descriptive names and descriptions for each parameter.

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's function: converting a placeholder reference into an HTML tag for email template insertion. The verb 'convert' and the resource 'placeholder reference' are specific, and it distinguishes this from sibling tools like hires_list_template_placeholders (which lists placeholders) and email template CRUD tools.

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 the tool is used when needing to insert a placeholder into an email template body, providing clear context. However, it does not explicitly mention alternatives or when not to use this tool, so it falls short of a full 'when/when-not' guideline.

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